|
You should have asked in Q&A
It is probably running Linux.
So you have learned something today:
With Linux, changing the network name requires a reboot or restarting the network.
|
|
|
|
|
It's Linux - or at least the Penguin logo appears on DNLA scans. I figured it would be, all my other ones have been Linux based (but I've never had this problem before).
And I am now ready to start thinking about copying from old NAS to new NAS - which looks like it's going to take FTP via the PC, damnit! 3TB of FTP...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
No SMB/CIFS (Samba) or NFS on the new one or both?
If you can use telnet or SSH to log into one of your NAS you can transfer the files via command line when mounting the shares of the other NAS.
|
|
|
|
|
Please, assume I know nothing about Linux: you'd be very, very close! (I used Unix about 30 years ago, but I can remember little of it these days).
I know the new one has CIFS (it talks about them when creating shares, and Windows sees them) and I know the old one supports SMB (because I use smb://ANAS/... when streaming from it to Chromecast).
But I have no idea what telnet or SSH involves.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
not laughing
veni bibi saltavi
|
|
|
|
|
For many, the reaction is probably "what, you didn't know this?", but I just found out that basic math is broken in GWT[^].
That's the sort of thing that probably warrants a huge warning on the home page of the project, but whatever, let's hide it in the docs that no one reads. "Write Java run JS" you say? Nope, you have to carefully "JSify" your Java in order to make it correct. Have you ever copied and pasted some Java code in GWT and made it run client-side? Be extremely worried.
How the hell is this acceptable? It could easily add the right amount of |0 in the right places to make most of it work right, that's not even slow. Multiplication in some cases (by large constants or two variables with each other) requires some slower JS code to be correct, but whatever, it's a compilers job to be correct first and fast second - speed does not compensate for incorrectness.
|
|
|
|
|
Phew, I thought for a second you were getting involved in the Global Warming Theory
You cant outrun the world, but there is no harm in getting a head start
Real stupidity beats artificial intelligence every time.
|
|
|
|
|
Just started working on a project which uses GWT.
Options like Angular exist, but we're firmly with GWT, and all its quirks
By order.
|
|
|
|
|
In what way? Cache doesn't honor Order of Operations.
|
|
|
|
|
...is a pain in the ass.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
And this is why I use Bootstrap. A lot of that rear end pain has been removed already.
|
|
|
|
|
if you design for a widescreen and a phone in responsive then IMHO it looks and works terrible, better to have a big screen UI and a phone UI
You cant outrun the world, but there is no harm in getting a head start
Real stupidity beats artificial intelligence every time.
|
|
|
|
|
Actually, I'm thinkin' you need a PC, tablet, and phone UI...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
you can go mad that way lol
you can get decent results with pc - Tablet UI and phone UI after that and its personal choice
You cant outrun the world, but there is no harm in getting a head start
Real stupidity beats artificial intelligence every time.
|
|
|
|
|
John Simmons / outlaw programmer wrote: I'm thinkin' you need a PC, tablet, and phone UI
I'm thinking you are right.
Once you lose your pride the rest is easy.
In the end, only three things matter: how much you loved, how gently you lived, and how gracefully you let go of things not meant for you. – Buddha
Simply Elegant Designs JimmyRopes Designs
|
|
|
|
|
Arghh! Just posted the same thing!
How do you know so much about swallows? Well, you have to know these things when you're a king, you know.
modified 31-Aug-21 21:01pm.
|
|
|
|
|
I thought there was an echo
You cant outrun the world, but there is no harm in getting a head start
Real stupidity beats artificial intelligence every time.
|
|
|
|
|
Well, i'm using bootstrap, and it ain't exactly cut and dried. I'm using a "responsive" coming-soon layout that I downloaded. On the iPad, it seems to work reasonably well (except for rotating which I thimk is a Safari issue). On my phone (Android S5 using Chrome):
- the image I'm using doesn't get reasonably small enough to be mostly visible. I can understand this in portrait mode, but in landscape, well, you know...
- all of the text on the right side of the screen is not on the device's display. This includes the "COMING SOON" text, and the copyright notice. This is true in both landscape and portrait mode.
It appears as if I have to do some css @media calls to size the divs and text based on maximum and minimum screen resolutions. I also have to evidently provide lower-resolution images to maintain some sort of control over bandwidth issues. I suspect this is also how I control how much of the image is displayed in portrait/landscape modes.
Even after 20 years, web development is still a pain in the ass (if not more-so than when it first started out).
If you want to see it on your phone, go here[^].
EDIT ======================
Oh wait, I just need to scroll down. I guess that's sorta acceptable...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
modified 20-Apr-15 10:06am.
|
|
|
|
|
Responsive website design development is a lot easier using Bootstrap
How do you know so much about swallows? Well, you have to know these things when you're a king, you know.
modified 31-Aug-21 21:01pm.
|
|
|
|
|
I'm using bootstrap.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Bootstrap LESS source?
How do you know so much about swallows? Well, you have to know these things when you're a king, you know.
modified 31-Aug-21 21:01pm.
|
|
|
|
|
Is that a "are you using it" question, or a suggestion?
Either way, I'm not sure how that would mitigate the problem of responsive design,. I know it's a big help for theming, but I would not consider themes to be part of responsive design...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
John Simmons / outlaw programmer wrote:
Is that a "are you using it" question, or a suggestion? |
More of a suggestion I guess.. I just find it makes it easier to build in the things you actually need rather than trying to undo default Bootstrap bits and bobs (meaning Bootstraps working against you in some scenarios).
I suppose if you're talking more about the design bit than the development bit, then it's probably more helpful to get some kinds of wireframe designs for each target screen size put down at the beginning rather than trying to work it out along the way.
Often there's functionality that just isn't relevant or feasible to include on a phone that works well on a tablet or desktop device.
Like Bergholt mentioned, if your phone UI (and/or functionality) starts getting too far away from the UI for other devices, then it's probably time to split them into different sites. So far, I've not found many sites that really need to be split up, but sometimes it's easier.
How do you know so much about swallows? Well, you have to know these things when you're a king, you know.
modified 31-Aug-21 21:01pm.
|
|
|
|
|
Yeah, I have one form that will have probably 50 or so fields on it. While the intent isn't to design the forms for mobile devices, I suspect some folks will - at the very least - want to enter that data from an iPad, so I'm gonna just assume that's how it's going to be done. Doing it on a phone will probably be painful, however, due to the diminutive screen size and the sheer number of fields.
The problem is that during development, it's kindof a pain because you have to test the site on five PC browsers, and then at least an iPad and a phone. I thnk I'm gonna have to buy an Android tablet, too, just for support reasons. Emulators are okay, I suppose, but the unanticipated problems don't seem to crop up until you're using the actual hardware. Fortunately, I have an intranet web server at the house, and I can deploy the site to it and test without it be outward-facing.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
John Simmons / outlaw programmer wrote: The problem is that during development, it's kindof a pain because you have to test the site on five PC browsers, and then at least an iPad and a phone.
Yep, that's a constant problem.
Where I am at the moment, the IT guys won't allow Macs or iPads (and I'm guessing Android devices too) to connect to the company network so we're having to go with best guess until we've got something we can access from the live interwebs.
Not ideal
How do you know so much about swallows? Well, you have to know these things when you're a king, you know.
modified 31-Aug-21 21:01pm.
|
|
|
|
|