On Sun, Jun 26, 2005 at 12:48:54PM +0200, Michael Herger wrote:
: Mike
: 
: >I got bored with the default Handheld skin and created "Handheld2"
: >(mostly a complete copy of Handheld with the status page looking
: >different) last night.  It's larger to load, but loads fine over
: 
: Removing the stuff you only commented out could help out.

Yeah, good point.  I'm too stuck in my server side processed land
where that wouldn't matter.  I'm not a big HTML user.


: I'll give it a try. As one who's using Handheld every day, I'm interested  
: in seeing what could be improved. Removing the first header line seems to  
: be a very simple, but effective change...
: 
: BTW: the following files aren't needed any more, they've been removed  
: recently.
: 
: badpath.html
: browse.html
: browseid3_artwork.html
: browseid3.html
: browseid3_list.html
: browse_list.html
: browse_playlist_list.html

Ah, thanks, I'll yank them out.

The tarball is updated with the two above changes made;

http://www.mikeb.org/handheld2.tar.gz


: >On a side note, the default PalmOS web browser doesn't understand
: >CSS or inline styles, so when designing Handheld skins they shouldn't
: >include them.
: 
: Why not? They're not hurting you, but improving the layout considerably on  
: eg. Opera (yes, Opera, on my PDA or future mobile phone). The skin  
: originally was created without any CSS and was working fine on the  
: author's Pocket IE. I added a _little_ bit to improve the layout on Opera.  
: But this shouldn't change the original work if your browser does not  
: understand it.

If your styles are only adding to the appearance in other places,
but not detracting from it in others, then it does not apply to
what I had meant.  For instance, you'll notice in the commented out
HTML I had some <hr>'s with inline styles;

<hr style="color:white;border:0px;margin:0px;height:1px"/>

I was using the thin white lines to separate each section, which
looked great in firefox where I was testing.  Unfortunately
Blazer (palmOne Blazer v4.0 to be exact) put in full width/ugly
hrs.  Two lessons learned; I had no idea what CSS/styles were to
begin the evening, then after learning how to use them I had to go
replace them all with <font> tags and comment out the hrs.

I just didn't want anyone else to go through the same pain =).


Thanks for the input Michael.

--mikeb
_______________________________________________
Discuss mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/discuss

Reply via email to