Hello to all Pebble fans and devs,
I have installed my nth version on pebble and stumbled on the same old
problems in adapting it to my CSS needs: the limit of the themes reach. I
invariably find myself editing the searchResult jsp to add to the TR and
TDs IDs and classNames. The ReadMoreDecorator is just appending a <a href>
to the excerpt of the entries, making it impossible to target in any CSS.
Adding a few JS files for minor tweaking. But they cannot be edited in the
theme file explorer... In which you cannot create a file but just upload
one - useless on an iPad for example.
These are a few examples of issues I have with right now.
Don't get me wrong, I love pebble and would not settle for anything else
today. But I'm French, so I like to complain a lot ;-)
One other issue I did myself struggling with is posting from a mobile
device. I take the train every day and end up spending quite a lot of time
on my smartphone. With on and off connectivity.
Gmail did set an example there with a very functional UI and autosave
features that rarely leaves you with unsaved work. Between local storage
and a regular draft save, it's been a long time since I lost any data in
gmail.
I am ready to help and propose patches on these areas, but first I'd like
to discuss it a with the community, to see if these changes are in line
with Pebble philosophy. If so, I'm completely open to advices, directions
and general tips in the best way to incorporate such changes into Pebble.
To summarize, I'd like to:
1. Add more classNames and IDs to objects for easy CSS targeting.
2. Delegate a little more stuff to the themes (blogEntry comes to mind).
3. Make JS files editable in themes - maybe even syntax highlighting for
the few file types editable. Also creating an empty file.
4. Make all the back end stuff in general more usable (notably on mobile
devices and modern browsers)
5. Making small changes here and there, such as adding "subtitle" to the
SearchHit class (useful for search result templating) or not generating the
subtitle H2 on a blog entry whose subtitle is empty. So that no empty H2 is
generated.
6. Maybe creating a "responsive" theme that may be included in the default
release (or responsiveizing the current default theme) making it more
suitable for today's modern browsing machines. Note that these changes
might not even affect the L&F of Pebble on a screen larger than 1000
pixels. Just a few media queries for small screens might just make the
trick if #1 is there.
For reference, my latest pebble instance: http://pieroxy.net
Now, be reassured, I'm not proposing my design, logos or colors - I know
where my artistic capabilities lies ;-) I'm just proposing a default Pebble
that would be easier to get there.
Well, that was a long mail, and if you got through it, thank you. I'd love
to hear your thoughts (most likely on a point by point basis)
--
Pieroxy
------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
Pebble-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pebble-user
