Ask / Submit

Revision history [back]

click to hide/show revision 1
initial version

posted 2013-12-30 02:16:03 +0300

dont' invent basic core/UI app that exist, just improve/adapt it

dont' invent basic UI/core app that exist, just optimize/adapt feature to UI/core and remove uncessary heavy code if exist without loose precious time ?

exemple: keyboard or keypad alphanumeric on SymbianOS S^3 with really useful function already exist but not exist on SailfishOS, why ? or maybe already planned for next month January, not next six month ?

Why forget/ignore basic function from former/older programmer like SymbianOS ? I know, is not just copy and paste, i can understand. some time, i have very difficult why a developer try to reinvent the wheel from scratch except for real unexisting feature/core

dont' invent basic core/UI app that exist, just improve/adapt it

dont' invent basic UI/core app that exist, just optimize/adapt feature to UI/core and remove uncessary heavy code if exist without loose precious time ?

exemple: keyboard or keypad alphanumeric on SymbianOS S^3 with really useful function already exist but not exist on SailfishOS, why ? or maybe already planned for next month January, not next six month ?

Why forget/ignore basic function from former/older programmer like SymbianOS ? I know, is not just copy and paste, i can understand. some understand.

Some time, i have very difficult why a developer try to reinvent the wheel from scratch except for real unexisting feature/core

dont' invent basic core/UI app that exist, just improve/adapt it

dont' invent basic UI/core app that exist, just optimize/adapt feature to UI/core and remove uncessary heavy code if exist without loose precious time ?

exemple: keyboard or keypad alphanumeric on SymbianOS S^3 with really useful function already exist but not exist on SailfishOS, why ? or maybe already planned for next month January, not next six month ?

Why forget/ignore basic function from former/older programmer like SymbianOS ? I know, is not just copy and paste, i can understand.

Some time, i have very difficult why a developer try to reinvent the wheel from scratch except for real unexisting feature/core

update... From FOSDEM2014 New technology: libhybris, leverage existing Android hardware adaptations. ● Drop X11 and focus on modern UI but don't reinvent the wheel. Use Wayland (see why next) ● Develop UI with existing working Wayland stack (Mesa/LLVMpipe on VirtualBox/X86) while we build the HW adaptation ● Use QtCompositor to fulfill the wildest dreams of our designers. ● The result you can see in the following slides: a productised (not a mockup – end-users use it as their daily devices) future proof mobile platform.

dont' invent basic core/UI app that exist, just improve/adapt it

dont' invent basic UI/core app that exist, just optimize/adapt feature to UI/core and remove uncessary heavy code if exist without loose precious time ?

exemple: keyboard or keypad alphanumeric on SymbianOS S^3 with really useful function already exist but not exist on SailfishOS, why ? or maybe already planned for next month January, not next six month ?

Why forget/ignore basic function from former/older programmer like SymbianOS ? I know, is not just copy and paste, i can understand.

Some time, i have very difficult why a developer try to reinvent the wheel from scratch except for real unexisting feature/core

update... From FOSDEM2014 New technology: libhybris, leverage existing Android hardware adaptations. ● adaptations.

  • Drop X11 and focus on modern UI but don't reinvent the wheel. Use Wayland (see why next) ● next)
  • Develop UI with existing working Wayland stack (Mesa/LLVMpipe on VirtualBox/X86) while we build the HW adaptation ● adaptation
  • Use QtCompositor to fulfill the wildest dreams of our designers. ● designers.
  • The result you can see in the following slides: a productised (not a mockup – end-users use it as their daily devices) future proof mobile platform.

dont' invent basic core/UI app that exist, just improve/adapt it

dont' invent basic UI/core app that exist, just optimize/adapt feature to UI/core and remove uncessary heavy code if exist without loose precious time ?

exemple: keyboard or keypad alphanumeric on SymbianOS S^3 with really useful function already exist but not exist on SailfishOS, why ? or maybe already planned for next month January, not next six month ?

Why forget/ignore basic function from former/older programmer like SymbianOS ? I know, is not just copy and paste, i can understand.

Some time, i have very difficult why a developer try to reinvent the wheel from scratch except for real unexisting feature/core

update... From FOSDEM2014 Development of SailfishOS 1.0

  • New technology: libhybris, leverage existing Android hardware adaptations.

    • Drop X11 and focus on modern UI but don't reinvent the wheel. Use Wayland (see why next)
    • Develop UI with existing working Wayland stack (Mesa/LLVMpipe on VirtualBox/X86) while we build the HW adaptation
    • Use QtCompositor to fulfill the wildest dreams of our designers.
    • The result you can see in the following slides: a productised (not a mockup – end-users use it as their daily devices) future proof mobile platform.

dont' invent basic core/UI app that exist, just improve/adapt it

dont' invent basic UI/core app that exist, just optimize/adapt feature to UI/core and remove uncessary heavy code if exist without loose precious time ?

exemple: keyboard or keypad alphanumeric on SymbianOS S^3 with really useful function already exist but not exist on SailfishOS, why ? or maybe already planned for next month January, not next six month ?

Why forget/ignore basic function from former/older programmer like SymbianOS ? I know, is not just copy and paste, i can understand.

Some time, i have very difficult why a developer try to reinvent the wheel from scratch except for real unexisting feature/core

From FOSDEM2014 Development of SailfishOS 1.0

  • New technology: libhybris, leverage existing Android hardware adaptations.
  • Drop X11 and focus on modern UI but don't reinvent the wheel. Use Wayland (see why next)
  • Develop UI with existing working Wayland stack (Mesa/LLVMpipe on VirtualBox/X86) while we build the HW adaptation
  • Use QtCompositor to fulfill the wildest dreams of our designers.
  • The result you can see in the following slides: a productised (not a mockup – end-users use it as their daily devices) future proof mobile platform.