pouët.net

Go in your pouet user settings > decrease amount of stuff shown in each page > done \o/

Gloom, thats why i argue in favor of a mobile webdesign

@PulkoMandy

But.. I like the default pouet on the desktop, I would like a reduced mobile friendly version on my phone.

xeron, create a "mobilexeron" account on pouet? :)

rasmus: since I work in mobile I tend to always ask what the app is going to actually DO when people say "We should make an app!" - 15 minutes later, most app projects are canceled.

Its simple.. visit "www.theregister.co.uk" on your desktop. Then, visit "m.theregister.co.uk" on your phone.

Thats the kind of thing i'd like for pouet...

pouet.net-->mobile end device detection/redirection with appropriate settings/layout (using WURFL or whatnot, I know it's not working 100%)-->done

or: mobile.pouet.net-->done

or: both

Hee hee, I see what you did there.

Yes, it has "mobile" as a suffix and yes, it does it utmost to emulate a touch-based native UI. But it's hardly a light-weight solution, requiring jQuery and all...

It's pretty nice for a self-contained webapp, but for a website like pouet, for a mobile scenario at that? I'd think twice before implementing it.

So, basically just a separate CSS if the site is viewed from a mobile phone? Easy.

gloom: A dumbed-down, slicker page layout to got with that would be preferable. That new layout posted a couple of times before is better, but a lot of the stuff on the homepage is probably not useful for a mobile user.

What would you need? Oneliner, news, BBS, latest added/released prods, maybe top of the month and search, all customizable in account->custom->mobilelobsteristic over 9000

Experience has it that the use case between desktop and mobile will be different, even for the same user -I fear for yet another account.php -mobile settings :)

I think, pouet.net could be easily converted. Just take the title of the "boxes" from the main page as menu entries and the content of the boxes as second pages and so forth.

Making a native mobile app of pouet.net is wasted energy. Keep the logic on the server, just create a different HTML interface for mobile phones, so its easy to handle with the pizza infested fingers.

Shifter: it could indeed save on both transfer and rendering-time with minimal effort, yeah.

are we talking about the same thing? I suggest mobile.pouet.net uses (a different layout, but also) a different set of customizable settings per account. The mobile default would be to have a reduced set of main page blocks (Oneliner, news, BBS, latest added/released prods, maybe top of the month and search).

If anyone is seriously going to do a mobile version of the site, I have 1 request: embed any youtube videos in the prod page. On the desktop it might be a controversial move, on mobile it's a seriously huge feature.

It would appear we do! :)

psionice: that's actually a really good feature request!

Oh come on, just roll the mobile site yourself already. Just talk to the Pouet API and off you go.

(talk to gargaj for an API key)

the pouet2.0 basecode i wrote has pretty good support for multiple layouts and all that, as well as the index page being entirely plug-and-render.

the reason it's so far behind still is because the database is broken as shit, and worst of all it relies way too heavily on SceneID, which itself suffers from the same problem.

i made a 2.0 version of sceneid quite some time ago which makes the functionality more streamlined and easier to maintain, but we never got to test it because we agreed with knos that he'd do some testing, then a week later he quit scene.org, so that sorta died there and the whole db collaction/charset setup is so intricately shit that i didnt dare to touch it alone. (and there's another hilaaaaaaaarious issue which i best not mention in public.) the way i see it, conversion of pouet from 1.0 to 2.0 will need at least a day of downtime to convert the db anyway.

bottom line is this - converting pouet to 2.0 has to start with updating sceneid to 2.0, utf8, all that crap. scene.org currently has one webcoder: me. i talked to ziphoid about it at KG _last_ year and he was adamant that he'd help, but that also sorta died. so if there's anyone who's 1) willing 2) capable and 3) persistent enough to help with testing this crap (sceneid, not pouet) out, it might get some gears rolling.

i apologize that there hasn't been much progress about this as there should've, but you gotta understand that pouet is way too fucking big to break, and sceneid is the rest of the iceberg.

note that by testing i didn't mean via an interface. i meant writing php code that uses the API attempts to break it.

Gargaj: I'm still very much interested in helping out, so let's do it! :P

Gargaj, I had no idea we talked about the sceneid testing this close to my decision to resign. I did not mean to do any harm here, please accept my apology.

knos: i wasn't implying anything, but it did happen weirdly close enough, so i was wondering if it was a statement about my code quality :D