Related
Pandora's Kitchen Option Utility
This utility will allow you to quickly save or recover your settings when customizing the options to your taste.
You will no longer have to go through BuildOS and check all your favorite programs every time you rebuild your image or install a new kitchen set.
Simply define your settings once, and from then on it's but a few clicks away
Troubleshooting:
If you receive an error when clicking "Load Kitchen":
1. The error message will display the path to the file. Check that it is formatted properly. See further down troubleshooting for more info.
2. Under the menu option File is the selection Log File. Click this to open the current log file for the kitchen you attempted to use. The last few lines should point to the option.xml file that caused the error.
3. Try running BuildOS. If it won't open, don't expect this to work. Try to isolate the trouble package and compare to other working ones.
Option.xml file formatting issues:
The file must be saved as Unicode
The file must follow the following format - noting that the entry for Tip is optional and the indention spacing is not displaying properly:
<?xml version="1.0" encoding="UTF-16" standalone="yes"?>
<Items>
<Item name="Time Sync Tab" group="Registry Tweaks" checked="false">
<Tip>Add time sync Tab to Phone Settings</Tip>
<Guid type="p">2f1ae013-04e8-11dc-8314-0800200c9a66</Guid>
</Item>
</Items>
Can't load Saved Configuration:
Your configuration file may have corrupted. Retrieve a backup or recreate it.
Known MAJOR Issues:
No known
Known Deficiencies:
List sorted by in alphabetical order
Future build will integrate BuildOS functionality - single user interface for both
once updated, option.xml files no longer use <cr> for readability. No effect on performance or function.
v1.0 Beta 1 does not read / edit the SYS folder option.xml file(s).
Downloads:
Installer:
Public Beta coming soon... target release of 10/10/07
.NET Framework 2.0 Redistributable (required if you don't already have it on your PC)
RapidShare Link
Revision History:
v1.00 Beta 1: Initial limited beta release
How-to video:
RapidShare Link (updated 10/9/07)
Suggestions:
Word to the wise - BACK UP YOUR KITCHEN!! It will save you much headache should something go wrong.
I can only rub my hands in glee - really look forward to using this as it allows for formal comparative testing between builds for me ;-)
Looks great Matt,
one question, how east is it to update the OEM packages. Same as before,just put them into the kitchen folder?
allan1 said:
Looks great Matt,
one question, how east is it to update the OEM packages. Same as before,just put them into the kitchen folder?
Click to expand...
Click to collapse
Very, then run this utility to set your options to true/false as you desire, then backup the settings so you can easily re-set them if you download a whole new setup.
Super easy and super quick. Just have a few XML formatting issues to resolve before I can get this out
News?
It sounds so good....
i'm getting excited
You're a good egg, you!
are we any closer to a beta yet?
Hi all, i am cooking my custom Kaiser / TILT ROM, i am using Spanish HTC lastest ROM, so i change some lines in initflashfiles.txt to put all things where suppose to go, but i have a issue with Start Menu because Spanish language have a "TILDÉ" and the Start Menu folder´s name its "Menú Inicio", so when i cook the ROM some apps shorcuts are created in "Men[] Inicio" (With a square instead the "TILDE"), i dont know how to setup the lines to work,
example...
Code:
;This will autolaunch this app and have it show on the Today screen in the task bar.
;Directory("\Windows\Startup"):-File("ShutXP.lnk","\Windows\ShutXP.lnk")
;This will just place a link in the Start Menu
Directory("\Windows\Start Menu\Programs"):-File("psShutXP.lnk","\Windows\psShutXP.lnk")
SPANISH LINES
Code:
;This will autolaunch this app and have it show on the Today screen in the task bar.
;Directory("\Windows\Inicio"):-File("ShutXP.lnk","\Windows\ShutXP.lnk")
;This will just place a link in the Start Menu
Directory("\Windows\Menú Inicio\Programas"):-File("psShutXP.lnk","\Windows\psShutXP.lnk") [B]<-----
THIS LINE CREATE THE FOLDER "PROGRAMAS" BUT ITS MAKE IT ON "MEN[] INICIO"[/B]
Any one can help me?
Regards!!
Try copying original, previously defined line (using HexEdit if "regular" Ctrl+C - Ctrl+V fails),
remember about Unicode...
nice, that mean i have to use a HEX editor instead a normal text editor?
any help? cant do the TILDE on hex editor!!!"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thread to be used for development discussions only, install issues etc use the release thread:
[MOD][23MAR10][v1.0][SENSE2.5TAB] Basic Facebook Tab
http://forum.xda-developers.com/showthread.php?t=651007
Thread Quicklinks:
2.5.192x issue and ROMs with older facebook engine...
v1.5 Released, v2.0 Development starts here [Post#361+]
v1.5 Beta Testing details start here [Post#133+]
Information for v1.5 language files & beta drafts [Post#109+]
I'll fill in more detail here when we start doing development work.
I've placed an OLD release into the groups 4shared directory, in the projects folder.
http://manila.4shared.com
Also my tutorial (which is more a notepad at the moment) is here:
TUT Manila Tutorial 4 - Placeholder/Facebook Tab
Setup Instructions
Setup Instructions (roughly):
1. Use the Command Line Kitchen (http://forum.xda-developers.com/showthread.php?t=528548).
2. Recommend 1st copying ALL xxxxxxxx_manila files from your windows dir (keep a copy as backup too), and decompile them all using the kitchen.
3. Rename the Workspace to something else (i.e. Workspace_complete), you can use this now as reference!
4. Start again with the manila files you want to work on, you now have your "working" folder of lauc files etc.
5. Make use of the manilaHASH to convert between filenames and internal path/file references (recommend you keep a list of ones you find, you'll be surprised how useful it can be).
For editing, Programmer's Notepad is excellent, you can save your workspace, highlight the files for lauc and xml and also use the "find in files" search to find stuff in your "Workspace_complete" folder.
Useful Links
Temp Location for the stuff moved off the main thread (this post can them be referred to if the info is important):
MAIN THREAD POST #1:
-----
The stuff below will get replaced when the next version is released...
-----
This is my facebook tab, the project is a learning project, it will also have a supporting tutorial with full details of how it is built.
By it's nature the intention is it is freely available and totally open.
Before people ask, no I can't do comments, pokes, likes, notifications etc etc, I am cheating here and borrowing HTC function/pages and only changing what I have to, to obtain the function needed.
I shall attempt to add some more function soon, will be linking in with a exe which will hopefully talk to the facebook api. At the moment I am unsure how successful this will be, also what to do about facebook requiring an account to be linked with the app and how to keep multi-language support. This will become clearer as I work on it.
Also, as I start to adjust things to suit my changes, I expect to break a few things too, this will be because I don't always see the full range of HTC functionality as I test (i.e. Events etc).
Hopefully it does enough to keep everyone happy. I shall try to document the creation of the tab, but at the moment development work is 1st.
HTC has put in as much more functionality than I thought (I keep seeing new parts to it), but they also did a good job of hiding it!
Personally I think there are some excellent features and credit goes to the poor soul who got told it couldn't be a tab (this is for you and your hard work!).
Please understand, currently ALL the facebook function is by HTC, all the integration is by HTC. The MOD moves the tab and formats it to look nice and also adds some small features which I wanted (I wanted to do more but everyone was keen to have it too!). Formatting and the extras is what takes the time. If you see the 192X basic "basic tab" a simple move of the tab is a 5 min job!
I'm planning to do at least one update to this to add the bits I couldn't get going in time, plus to make it easier to configure via the settings instead of the registry. After that, I'll release a dev pack and facebok api could be added etc on top (but again must be a matter of time before we get an official one).
______
Latest WVGA Screens
Latest VGA Screens
MAIN THREAD POST #2:
-----------------------------------------
Details for v1.01 (to be removed later)
-----------------------------------------
Settings are all via the registry (for now). The "Download Data Automatically" etc in the settings subpage runs independently of the Automatic Update Period.
Registry Settings
Change these registry keys to change how it works.
[HKEY_CURRENT_USER\Software\HTC\Manila]
"Facebook.LaunchAppSel"=dword:1
Number added to Facebook.LaunchApp to determine which app is launched (entry must exist)
"Facebook.LaunchAppName0"="MS Facebook App"
"Facebook.LaunchApp0"="\\Windows\\Facebook.exe"
Path and filename of app, note \\ should be used in *.reg file to put \. Within the registry this will read as "\Windows\Facebook.exe"
"Facebook.LaunchAppArgs0"=""
Added to the end of the application call if required
"Facebook.LaunchAppName1"="Facebook IM App"
"Facebook.LaunchApp1"="\\Storage Card\\Program Files\\fim\\fim.exe"
"Facebook.LaunchAppArgs1"=""
2nd optional application. You can add any number of others at the moment.
"Facebook.LaunchWebSel"=dword:0
Same as "Facebook.LaunchAppSel" but for the web launch
"Facebook.LaunchWebName0"="Mobile Facebook"
"Facebook.LaunchWeb0"="m.facebook.com/"
"Facebook.LaunchWebArgs0"=""
"Facebook.LaunchWebName1"="iPhone Facebook"
"Facebook.LaunchWeb1"="touch.facebook.com/"
"Facebook.LaunchWebArgs1"=""
"Facebook.LaunchWebName2"="Desktop Facebook"
"Facebook.LaunchWeb2"="www.facebook.com/"
"Facebook.LaunchWebArgs2"=""
Same as "Facebook.LaunchApp#" but for the web launch
"Facebook.LastUpdateTime"=""
"Facebook.LastUpdateDate"=""
Stores the last update time/date used in the display, set by the program.
"Facebook.MyStatus"=""
Copy of your status text, set by the program, if its working ok
"Facebook.MyStatusExe"="\\Windows\\FacebookStatusUpdate.exe"
"Facebook.MyStatusScript"=""
Used to copy registry entry of My Status into the above key. Note: If you set Facebook.MyStatusExe blank, it won't try to update.
"Facebook.AutoUpdateInterval"=dword:0
Time in minutes between automatic updates. I think only runs when within the tab, set to 0 will disable automatic update (although independent of the 2 hour update on the settings page).
FAQ
Launch App/Web does not work (i.e. I get a Certificate error)
Chances are, you need to adjust the registry setting to point the selected application to the location where it is installed (or ensure you have the app installed).
Please see Agent Zach's guide here:
http://forum.xda-developers.com/showpost.php?p=6247589&postcount=470
Why do we need FacebookStatusUpdate.exe (or originally mortscript) and what does it do?
It's a limitation of what is in manila, you can only read from "HKCU\Software\HTC\Manila", unless you are only after a int value.
All the script does (or exe), is the following:
Code:
RegReadString("HKLM", "Software\HTC\FacebookSDK","Status",myStoredStatus)
RegWriteString("HKCU","Software\HTC\Manila","Facebook.MyStatus",myStoredStatus)
There may be a work around, but it would take a lot of time to test for something so simple.
MAIN POST #3:
=============================================
Below applies to v1.01 only - will be removed soon
=============================================
All-In-One Cab Install Instructions
Warnings etc
Modifying manila means various levels of messing around with the files on the device so, as with most of the mods on here, back-up often and be prepared to screw it up and hard-reset your device. All the changes explained here may or may-not work on your particular device/version of manila or perhaps it's just not going to happen today.
Instructions:
1) Ensure you have moved your tabs around at least once, via Settings Tab, this ensures the correct registry keys are present used by the cab install.
2) Run the cab and Install to Device (attached to first post).
3) Copy any language files which are missing if you need them into the windows directory (some are included).
4) If this does not work, then don't un-install, but follow the manual install instructions (ensure you copy all the files from the zip as instructed).
You don't even have to disable Sense first or anything. It'll do that, and re-start Sense for you. It's recommended to install it after a fresh hard reset for best results, but it may still work without doing so.
Thanks to Captain_Throwback for creating the cab and johncmolyneux for creating the executable that adds the correct info to the tab control file automatically so that the install is fully automated.
Please report any issues you have with the install here, so that we can try to fix them.
All-In-One Cab Uninstall Instructions
Will update soon, with precise details:
1. Replace the 26948339_manila file in your windows directory with the backup version made by the cab also in windows.
2. Then perform 5. Reset Manila as described in the manual install steps.
Note: Until this is updated, and you are not confident, you can simply disable the tab via Settings, Home Screen Tabs!
Latest: http://forum.xda-developers.com/showpost.php?p=6203074&postcount=434
Manila Sense Fix - Sense is not starting after install/uninstall
If you run into problems with Sense not starting then there are two things you can do.
1. Run moonnah's B_L_Group_FixStartManila_2.5.cab from the following thread (this should fix any problems with your tab control file):
http://forum.xda-developers.com/showthread.php?t=670116
2. Post your tab control file (26948339_manila) on the thread and we shall correct any problems and repost it.
The next release of All-In-One cab will hopefully run the FixStartManila for you so this issue will hopefully be fixed.
[USE ALL-IN-ONE CAB INSTEAD] Captain_Throwback's OLD Cab Install Instructions
I've just kept this section for now, until we are happy the all-in-one cab does what it needs to do. Let me know if you still have to use this method.
Note: 1084 views on this cab now - will monitor for use. OK removed the attached cab to avoid confusion.
Warnings etc
Modifying manila means various levels of messing around with the files on the device so, as with most of the mods on here, back-up often and be prepared to screw it up and hard-reset your device. All the changes explained here may or may-not work on your particular device/version of manila or perhaps it's just not going to happen today.
Captain_Throwback Post here
NOTE: This cab does NOT include the tab control file (26948339_manila). Because everyone's set of tabs is different, each will need to be edited individually, per the instructions HERE. The edited file should be copied AFTER the CAB is installed. The install will make a backup of your original file called "26948339_manila_orig", if you have issues with the edited file.
Instructions:
1) Install CAB (attached to this post)
2) Verify that Sense is disabled in Today items once install is complete.
3) Copy edited tab control file (26948339_manila) to \Windows folder on device. Confirm overwrite of existing file.
Either get your tab control file (26948339_manila) from \Windows folder and edit it yourself or use a pre-written one which matches all the tabs orginally listed in your Settings Tab (where you re-order the tabs).
Edit your 26948339_manila file from your \windows\ directory (you can use the example in the zip file \tabcontrol\ as a guide, use a UTF-16 Compatible Editor such as Notepad2 or Programmers Notepad.
a) Insert the following text, between the other "pages" defined, replacing the X with suitable number (re-numbering the others as required to avoid duplicated numbers):
Code:
<Page Order="X" Name="facebook.page" PackageName="HTC" Title="[[Facebook]]">
<ComponentReference Name="page" Mode9Path="HTC\People\facebook.mode9" Component="SummaryAllPage" SmartComponent="true"/>
<ComponentReference Name="icon_normal" Mode9Path="HTC\Manila\Facebookicon.mode9" Component="Facebook_Off"/>
<ComponentReference Name="icon_selected" Mode9Path="HTC\Manila\Facebookicon.mode9" Component="Facebook_On"/>
<ComponentReference Name="icon_preview" Mode9Path="HTC\Manila\Facebookicon.mode9" Component="Facebook_Preview"/>
</Page>
b) Copy back completed file to your device \windows\ directory
4) Re-enable Sense in Today items.
Manual Install Instructions (for use with the zip files)
Scott8813 has kindly provided a detailed tutorial on how to add the tab, so if you need more detail then please refer to this.
Manual Install Tutorial (Scott8813)
http://forum.xda-developers.com/showpost.php?p=6004802&postcount=216
Warnings etc
Modifying manila means various levels of messing around with the files on the device so, as with most of the mods on here, back-up often and be prepared to screw it up and hard-reset your device. All the changes explained here may or may-not work on your particular device/version of manila or perhaps it's just not going to happen today.
The files may be hidden system files (may need to enable viewing of system hidden files to find them)
Keep an original copy of your 26948339_manila file, particularly if you use a cab to install
If the tab doesn't work you can use it to restore things back (just do step 5)
1. Copy 26948339_manila from your \windows\ directory to your PC.
2. Copy all the files in the zip file \windows\ directory to your devices \windows\ directory.
3. Import the registry items from the "appFacebook.reg" file into your devices registry.
This will add new entries "Facebook.XXX" to "HKEY_CURRENT_USER\Software\HTC\Manila"
4. Create your Tab Control File:
Edit your 26948339_manila file from your \windows\ directory (you can use the example in the zip file \tabcontrol\ as a guide, use a UTF-16 Compatible Editor such as Notepad2 or Programmers Notepad.
a) Insert the following text, between the other "pages" defined, replacing the X with suitable number (re-numbering the others as required to avoid duplicated numbers):
Code:
<Page Order="X" Name="facebook.page" PackageName="HTC" Title="[[Facebook]]">
<ComponentReference Name="page" Mode9Path="HTC\People\facebook.mode9" Component="SummaryAllPage" SmartComponent="true"/>
<ComponentReference Name="icon_normal" Mode9Path="HTC\Manila\Facebookicon.mode9" Component="Facebook_Off"/>
<ComponentReference Name="icon_selected" Mode9Path="HTC\Manila\Facebookicon.mode9" Component="Facebook_On"/>
<ComponentReference Name="icon_preview" Mode9Path="HTC\Manila\Facebookicon.mode9" Component="Facebook_Preview"/>
</Page>
b) Copy back completed file to your device \windows\ directory
5. Reset Manila:
a) Delete "\\windows\manilaFull.xml" on your device (don't worry this is regenerated when manila restarts).
b) Delete the configuration reg-key HKLM\Software\HTC\Manila\Configuration (this resets the tab list and allows the new tab to be included in the tab re-ordering page of the settings tab - the keys only re-generate when you go back to that tab re-ordering page)
Alternative exe instead of mortscript (old zip version v1.0 23Mar10 ReleaseB):
Use the exe from FacebookStatusUpdate.zip and place in your windows folder (doesn't matter where, as long as you link correctly).
Change reg file to:
"Facebook.MyStatusExe"="\\Windows\\FacebookStatusUpdate.exe"
"Facebook.MyStatusScript"=""
Or directly in reg:
Facebook.MyStatusExe = "\Windows\FacebookStatusUpdate.exe"
Facebook.MyStatusScript =""
To Do List
Development To Do List:
Unreleased development work
Correct landscape view (remove space at top) - DONE (except displayed items are not refreshed)
Reduced reg key copies (less lag) - DONE
Improve extended char support for updates etc
Move birthday icon in expanded view - DONE
Provide "updating..." feedback when there is no Update Bar (for 1st run etc)
Build in wait state to tab, to catch when external app has completed operations (keep checking for reg key flag)
Character count for the status update page (xx/420).
API Phase 2
Development (from v1.01, released in v1.5):
People Link font colour - DONE
Allow view of full status text, either bigger space, expand on selection or ticker tape
- DONE (all expanded/colaspe view)
Improve autoupdate timer for entering tab - 20% INPROGRESS Leaving this as not a big issue.
Update settings page to include things set in registry (Auto Update time etc) - 100% DONE
Replace naff .Net fileopen dialogue with something usable - 100% DONE (thanks johncmolyneux)
Htc sense look for settings page - 100% DONE
Multi Language Support for exe - 100% DONE
Tie in to Facebook Api - Initial Tests 100% DONE - limited for release
Implement Fb Api Status Update - 100% DONE
File's Involved
Release v1.0 Uses the following files:
Code:
Graphics
4F90441E_manila \windows\htc\Common\Assets\Images\Common\VGA\facebook_divider.qtc
5D4F2200_manila \windows\htc\Assets\Images\Manila\icon_off\Facebook_tray.qtc
05FF1072_manila \windows\htc\Assets\Images\Manila\icon_preview\Facebook_large.qtc
06C09C86_manila \windows\htc\Common\Assets\Images\Common\facebookline.qtc
357374E7_manila \windows\htc\Assets\Images\Manila\icon_preview\Facebook_tray.qtc
Lang
35452D58_manila \windows\htc\people\locales\en-gb\facebook.en-gb.xml
5470CE36_manila \windows\htc\people\locales\en-us\facebook.en-us.xml
Luac
090EF4F3_manila \windows\htc\people\scripts\people\facebookpage.luac
Mode9
51B6F88A_manila \windows\htc\people\facebook.mode9
59B632C0_manila \windows\HTC\Manila\facebookicon.mode9
Tab Control
26948339_manila
Supporting
manila_xml\Facebook_Pages.xml
FacebookStatusScript.mscr
appFacebook.reg
Attached is my current list of filenames which I've used/worked on/browsed through etc.
subscribed! thanks for starting this thread,now i don't have to write more OT's in your main thread
etoy said:
subscribed! thanks for starting this thread,now i don't have to write more OT's in your main thread
Click to expand...
Click to collapse
No problem.
Gives me somewhere to write what I am up to without spamming my own thread too.
1. Currently I'm working on different views of the main page.
It's hard to see how events will be displayed since no-one I know uses them (how do they appear normally? Are they part of the individual status items?) Also, unable to change "Has Multiple Updates" to display the status and updated album message when there is more space, not a major issue. I'll post some screens at some-point.
2. Will then start to work on tying things into an exe which I can then experiment with the facebook api without having to wrestle with manila, plus for now I will put the tab specific settings page in it too (makes little difference visually to a manila sub-page, except I'm not sure how to pull in the translations for multi-lang).
3. Also starting to look at .\Scripts\People\peopleUpdateViewPage.luac 285D32BC_manila which is the more detailed tab when you select someone, but it's not fully decompiled so I've not tried changing it yet. Ideally I can put more info/options within this page when the fb api is functional.
4. Need to finish off the update timer, should be able to look at the time of the last update and update immediately even if you've just entered the tab. Currently it just waits for the update period, which only happens if the tab is open.
5. Need to put another text object on the main page for each fb item, hopefully for use with the fb api.
damn,i can't open that m9editor. if i'll not find other possibilities i'll have to run an xp-mode VM. i only managed to convert the 59B632C0_manila file to xml with mode9converter but it gives me an error when i try to convert back to mode9.
meltwater, please just edit it this way from "icon_off" to "icon_on" and attach me the edited manila file,i'll try to do the rest. thanks!
etoy said:
damn,i can't open that m9editor. if i'll not find other possibilities i'll have to run an xp-mode VM. i only managed to convert the 59B632C0_manila file to xml with mode9converter but it gives me an error when i try to convert back to mode9.
meltwater, please just edit it this way and upload me the edited manila file,i'll try to do the rest. thanks!
Click to expand...
Click to collapse
Ok done. Well timed checking of xda, there..a few mins difference.
Code:
<Movie>
<Property> Name=Platform Value="GLESPlatform"
<Locale>
<Directory> = Value=".\locales\"
<LibraryManager>
<Library>
<Character>Type="ComponentClipCharacter"
<Property> Name=LibraryID Value="6"
<Property> Name=Name Value="Facebook_Off"
<Object>Type="ComponentClip"
<Property> Name=Initial Play State Value="0"
<Group>
<Object>Type="GLESSprite2D"
<Property> Name=Disable Render Value=""
<Property> Name=Instance Name Value="iconButton"
<Property> Name=Position Value="PosX=-16 PosY=8 PosZ=0"
<Property> Name=Texture Path Value="..\Common\Assets\Images\Common\alpha-hitbox.qtc"
<Property> Name=Size Value="Width=96 Height=100"
<Object>Type="GLESSprite2D"
<Property> Name=Instance Name Value="iconButton1"
<Property> Name=Texture Path Value=".\..\Assets\Images\Manila\icon_off\Facebook_tray.qtc"
<Property> Name=Size Value="Width=140 Height=140"
<Character>Type="ComponentClipCharacter"
<Property> Name=LibraryID Value="7"
<Property> Name=Name Value="Facebook_On"
<Object>Type="ComponentClip"
<Property> Name=Initial Play State Value="0"
<Group>
<Object>Type="GLESSprite2D"
<Property> Name=Texture Path Value=".\..\Assets\Images\Manila\icon_on\Facebook_tray.qtc"
<Property> Name=Size Value="Width=140 Height=140"
<Character>Type="ComponentClipCharacter"
<Property> Name=LibraryID Value="8"
<Property> Name=Name Value="Facebook_Preview"
<Object>Type="ComponentClip"
<Property> Name=Initial Play State Value="0"
<Group>
<Object>Type="GLESSprite2D"
<Property> Name=Texture Path Value=".\..\Assets\Images\Manila\icon_preview\Facebook_large.qtc"
<Property> Name=Size Value="Width=300 Height=300"
<Scene>
<Property> Name=Initial Play State Value="0"
<Group>
<Object>Type="Component"
<CharacterReference> LibraryName=facebookicon.mode9 Value="6"
Looks like the right change, although will see what it does on my phone...ok doesn't break it which is good.
Now just need to get my hands on a full version of visual studio...
IT WORKS!
great we found the right reference,which results in:
1F04C842_manila \windows\htc\Assets\Images\Manila\icon_on\Facebook_tray.qtc
--
do you think the 357374E7_manila file is needed? it does not show anywhere..
--
i attached the right 1F04C842_manila file. now you can use it with your corrected 59B632C0_manila to have separated split icon on/icon off.
the "icon on" should be hi-res 16bpp and "icon off" 8bpp but cfc_gui did'em both at 8bpp not a big deal tho,and easily correctable.
i'm happy for my little contribution,now i have to research that last missing "rearrange tab" icon
etoy said:
IT WORKS!
--
do you think the 357374E7_manila file is needed? it does not show anywhere..
--
i attached the right 1F04C842_manila file. now you can use it with your corrected 59B632C0_manila to have separated split icon on/icon off.
the "icon on" should be hi-res 16bpp and "icon off" 8bpp but cfc_gui did'em both at 8bpp not a big deal tho,and easily correctable.
i'm happy for my little contribution,now i have to research that last missing "rearrange tab" icon
Click to expand...
Click to collapse
Ok, will try it out on my phone too. Donno about the 8bpp and cfc'ing can't remember what my originals were like.
Good luck with the "rearrange tab" I think the key is to find what the reference path/name is, either from the filenames or from the mode9 file whichever that one is.
Oddly, I've found it hard to find the colour settings for the title when in landscape mode, all the colours are in the mode9 file (but not that one it seems - changed all from R0G0B0 but it is still black...):
51B6F88A_manila \windows\htc\people\facebook.mode9
It might be using the theme colours instead (remember it was a sub-page so black is default), only found them yesterday so will chase that route 1st.
Been thinking about how to do the first page interface (depending on the fb api success of course). I think, ideally we want to drop the link to the People Tab sub-page and drive everything within the main tab page (ideally storing it's state if you leave the tab). It should then allow you to select someone, and the item expand, again you view comments etc, select them again and you get options to comment/like etc. Easy to suggest, but not anywhere near being able to do that within the manila yet, a nice aim though.
One issue I do see ahead is updating the information/storing it all, do we pick up live data when we open views (unlikely to be smooth) or attempt to download everything we need in one burst and store it away (I guess you could then open wifi, download and close wifi again...in theroy). Ideally we could use the same storage as the fbmgr uses, but I doubt that is accessible so may need duplicated info.
meltwater said:
Ok, will try it out on my phone too. Donno about the 8bpp and cfc'ing can't remember what my originals were like.
Good luck with the "rearrange tab" I think the key is to find what the reference path/name is, either from the filenames or from the mode9 file whichever that one is.
Click to expand...
Click to collapse
there are no direct references,or at least i did not find'em yet. unfortunately the other tabs' manila icon files don't have a group,they're "unknown" on cfc_gui. it was easier with slider and tab icons as they were in manila names.txt list. i found some interesting file this nite but it was late so i left some work for this evening
meltwater said:
Oddly, I've found it hard to find the colour settings for the title when in landscape mode, all the colours are in the mode9 file (but not that one it seems - changed all from R0G0B0 but it is still black...):
51B6F88A_manila \windows\htc\people\facebook.mode9
It might be using the theme colours instead, only found them yesterday so will chase that route 1st.
Click to expand...
Click to collapse
on my phone, in landscape mode, i don't have the facebook tab title at all not even the black one you talk about..
meltwater said:
Been thinking about how to do the first page interface (depending on the fb api success of course). I think, ideally we want to drop the link to the People Tab sub-page and drive everything within the main tab page (ideally storing it's state if you leave the tab). It should then allow you to select someone, and the item expand, again you view comments etc, select them again and you get options to comment/like etc. Easy to suggest, but not anywhere near being able to do that within the manila yet, a nice aim though.
One issue I do see ahead is updating the information/storing it all, do we pick up live data when we open views (unlikely to be smooth) or attempt to download everything we need in one burst and store it away (I guess you could then open wifi, download and close wifi again...in theroy).
Click to expand...
Click to collapse
that becomes a tad difficult to understand to me,sorry hope some skilled user will help you more with that. very curious to see what's possible to achieve with the facebook api tho.
etoy said:
there are no direct references,or at least i did not find'em yet. unfortunately the other tabs' manila icon files don't have a group,they're "unknown" on cfc_gui. it was easier with slider and tab icons as they were in manila names.txt list. i found some interesting file this nite but it was late so i left some work for this evening
Click to expand...
Click to collapse
Yep there are lots of interesting goodies within the files.
etoy said:
on my phone, in landscape mode, i don't have the facebook tab title at all not even the black one you talk about..
Click to expand...
Click to collapse
Ah, my background is black so I assumed it was just black too. Ok, will rethink that then. Maybe just a case of setting it visible...at the right point..at the right time. No logical reason why it's on the people tab but not this one, same code. Not too bothered about it yet.
etoy said:
that becomes too difficult to understand to me,sorry hope some skilled user will help you more with that. very curious to see what's possible to achieve with the facebook api tho.
Click to expand...
Click to collapse
I've found the editing of the gui the hardest so far, mainly because you can't see until you try but also if it doesn't like it, it gives up and moves on (so you can't even see where it was wrong). Still what started out as a little experiment on my part has already opened up a lot of what can be done. The Custom Manila Interface Tab is still a long term goal.
MS don't make it very easy to develop on windows mobile, they still don't have support for it in Visual Studio 2010 Express. I think I'll go for a trail version to get me started and then switch to non-MS solution once I'm happier. It's all new to me but keen to pick this up too.
Hi meltwater and etoy,
it is a help when i testing something too, because i was working also for that issue and i have found the same thing as you two. Strange, three people with the same thoughts. Not easy to find....
Ask me and will help. BTW, this is the dutch language file. I working on it, but a lot of translation:
6CD727C8_manila \windows\htc\people\locales\nl-nl\facebook.nl-nl.xml
meltwater said:
1. Currently I'm working on different views of the main page.
Click to expand...
Click to collapse
I think you was to much busy with co0kies new mod. But the idea is very good. Possible i can help out too
mike2nl said:
Hi meltwater and etoy,
it is a help when i testing something too, because i was working also for that issue and i have found the same thing as you two. Strange, three people with the same thoughts. Not easy to find....
Ask me and will help. BTW, this is the dutch language file. I working on it, but a lot of translation:
6CD727C8_manila \windows\htc\people\locales\nl-nl\facebook.nl-nl.xml
I think you was to much busy with co0kies new mod. But the idea is very good. Possible i can help out too
Click to expand...
Click to collapse
You can get most of it from:
\windows\htc\people\locales\nl-nl\peopleupdate.nl-nl.xml
35DC316_manila
Probably a little late to point that out...
All help is welcome. There should be a lot more as I implement more, but fixing the little bugs is very helpful.
It will get difficult to manage changes as we all get deeper into it, but at least the more we change the more files and area's of functionality there is to work on, so hopefully it will be possible.
meltwater said:
You can get most of it from:
\windows\htc\people\locales\nl-nl\peopleupdate.nl-nl.xml
35DC316_manila
Probably a little late to point that out...
Click to expand...
Click to collapse
Have you can say it 5 minuts earlier? Thanks for the info but that was also my thought to take some things that are allways done .
All help is welcome. There should be a lot more as I implement more, but fixing the little bugs is very helpful.
It will get difficult to manage changes as we all get deeper into it, but at least the more we change the more files and area's of functionality there is to work on, so hopefully it will be possible.
Click to expand...
Click to collapse
10 Ask me
20 me is waiting for info (source or whatever)
30 me send's response
40 goto 10
mike2nl said:
Have you can say it 5 minuts earlier? Thanks for the info but that was also my thought to take some things that are allways done .
10 Ask me
20 me is waiting for info (source or whatever)
30 me send's response
40 goto 10
Click to expand...
Click to collapse
10 Donno yet! What can you do / what do you want to do?
20 the source "is" the manila files (although I've started putting comments in my latest files - so will have source versions for later builds), you need to install the command line kitchen and decompile it (see the rough tips on this threads post #2).
30 go for it - ask away
40 Compile, reset manila. Bang head on table. Goto 10
At the moment, I've started working on the supporting exe which will handle the facebook api and settings etc, but I'm a beginner with windows mobile development so it'll take some time before I am up to speed with that and have something worth sharing (oh plus day job...).
qitt said:
meltwater
Thank you for your great mod. I finally investigate the name of file "icon in rearrange tab". The name must be 6BEE887F_manila. Hope it helps you.
Click to expand...
Click to collapse
OK, looks like we have another fix!
Ok, so I tried this . . .
I used my CFC graphics files, and replaced them in the All-in-One CAB. I replaced the updated file from the first page that had the updated mode9(?) code, and I copied the manila file and pasted it as "6BEE887F_manila" (I retained the original file some said 'wasn't needed' anyway). I now have the icon in the Customize tabs screen, but I'm missing the icon when the tab is selected. Is it because I didn't delete the "357374E7_manila" file? Is it just me that has this issue? The icon is there when the tab is not selected, and the large version is fine. That's the only one that's missing now (and previously, it was fine ).
Captain_Throwback said:
I used my CFC graphics files, and replaced them in the All-in-One CAB. I replaced the updated file from the first page that had the updated mode9(?) code, and I copied the manila file and pasted it as "6BEE887F_manila" (I retained the original file some said 'wasn't needed' anyway). I now have the icon in the Customize tabs screen, but I'm missing the icon when the tab is selected. Is it because I didn't delete the "357374E7_manila" file? Is it just me that has this issue? The icon is there when the tab is not selected, and the large version is fine. That's the only one that's missing now (and previously, it was fine ).
Click to expand...
Click to collapse
Don't delete 357374E7_manila, it's slider icon. Just create 6BEE887F_manila from scratch or using existing files from rearrange tab.
qitt said:
Don't delete 357374E7_manila, it's slider icon. Just create 6BEE887F_manila from scratch or using existing files from rearrange tab.
Click to expand...
Click to collapse
So I can't copy "357374E7_manila" and paste as "6BEE887F_manila" (that's what I did - I didn't delete any files)? That doesn't explain why my slider icon is missing when the tab is selected ?
Are you interested in making or editing a CHT widget? To make a widget for Co0kie Home Tab 2.0.0 is not such a difficult job as you may think, I tell you by experience. I have no previous formation in programs or informatic code but i could make a few widgets(*) and I would like to share this experience with you. This is not so altruistic work, I am expecting a huge amount of widgets made by all of you to install and enjoy in my brand-repaired HD2
Co0kie Master has allready published a guide for making a CHT widget (it is into the widgets kitchen); also Genius_Rat_2665 has made a tutorial for making a cht clock widget, so -the third time lucky- lets bring here all that knowledge and try to make a simple widget step-by-step. Also this could be a good place to share and learn each other some code for widgets. Things like how to make an blinking element, how to change number in text, how to read from the registry, etc.
(*) What is for sure is that no one widget I could ever do without the help of others. Lets start quoting the existing Co0kie's guide:
Here is a guide on how to build your own widget for CHT.
I decided to break this up into 3 parts.
The kitchen section is a brief description of the kitchen structure and batch files.
The guide section will tell you how to build your own widget and make a cab to install it.
The "how it works" section will tell you what's going on in the background - why the system is the way it is.
#####################
*** 1) Kitchen ******
#####################
Just a few words about the kitchen folder structure:
- Workspace - here you'll find all the raw files that are being worked on currently
- Tools - all the needed tools
- deploy - just a little temp dir used by the batch scripts to compile and deploy files directly to your device
- cab - the cab file and setup.dll
- cab\_files_final - all the final compiled files that will need to be inside the cab
The batch files:
These files automate the process of editing manila files.
Connect your device to your PC via ActiveSync to be able to run the batches.
z_init.bat - You need to run this one before starting. You just need to run it one time. It will copy restartmanila.exe to you device.
_Deploy_to_device_in_dev_mode.bat - this batch will:
1) compile the lua files from \workspace\_lua and copy them to the deploy folder
2) copy all files from \workspace\mode9 and other \workspace\ subfolders to the deploy folder
3) use rapicopy.exe to copy everything from the deploy folder to \windows on your device (it's set to overwrite exitsting files)
4) restart manila on your device
_Generate_files_for_cab.bat - this will compile and copy the workspace files but it will not deploy them to your device,
instead it will copy them to \cab\_final_files
it will also rename the base mode9 and lua files to CHTmode9 and CHTlua - more on this in the "how it works" section
[[ It also needs to be modified the files _Generate_files_for_cab.bat & _Deploy_to_device_in_dev_mode.bat to addapt them to your own widget. Click with the right button of the mouse over the files and select edit, then change the name of the widget (PoyTEST.lua & PoyTESTtranslation.lua in the attached example) and the corresponding manila files ]]
[[ Tools folder includes m9editor for the edition of mode9 files, notepad2 for the edition of the Lua files, CFC_GUI for the qtc files (graphics), manilaHASH to obtain the right manila names corresponding to .luac files, and some other .exe files used automatically by the kitchen. ]]
################################
*** 2) Making your widget ******
################################
Guide - how to make CHT addon widgets:
First of all, because you will be developing, you need to turn on CHT's dev mode.
Open the reg key HKCU\Software\HTC\Manila\ and create a DWORD value, call it "CHTI.AddonWidgets.DevMode" and set it to 1.
This will allow you to deploy and test your widget directly from the kitchen.
[[ This is very important as you do not need to create and install the cab for test the widget, just using DevMode the widget will go from \workspace\ directly to your device, so you can make changes and see results easily. ]]
Now proceed to build your widget. I suggest you use the analog clock addon as a base. [[ You can use PoyTEST, its much simplier ]]
There are two rules you simply must follow:
1) For every new widget, its CHTWidgetDev.lua file must change the "widgetName" property. It must something unique.
I suggest a naming system of "CreatorName_WidgetName" - that should ensure that the names are unique - there must not any conflict here!
Modify anything else however you'd like. The rest of the fields in that file don't need to be as unique as the "widgetName" property.
2) The 30182CB6_manila mode9 file must follow a special rule: The "Scene" section must not contain any components. See how it looks like in the example addon.
That's how it must look for all new widgets.
[[ Making a widget is like making a puzzle (but much more funny ), you have to put the right pieces in the right places. There is no a fix rule and there is a lot of trial and error. Where to find the right pieces? Co0kie gave us thousand of decompiled lines of Lua code in CHT_Source. Download it from post#6 of CHT 2.0.0 thread. Also look in every published widget's kitchen in CHT thread, Rat_2665, Dunc0001, ZaxXx, Azarbel, Colossus_r, RoryB, MnCessna ... (Sorry I dont remember all right now!) ]]
Once you've done that you can do ahead and run "_Deploy_to_device_in_dev_mode.bat" - that will compile the files, copy them to your device and restart manila.
Then just go to the edit widget menu in CHT - your widget should be at the bottom of the list - add it and test it.
When you have finished making your widget, you can pack it up into a cab file.
To prepare the files for the cab you have to run "_Generate_files_for_cab.bat".
The final files will be in the \cab\_files_final\ folder.
Making the cab file - this is what an addon cab must have:
1) Every last one of those files from \cab\_files_final\ need to be in the cab and they have to be set to be copied to %windows%.
Do NOT set the install dir to %windows%, set the files to be copied to %windows%.
2) The setup.dll that is in the \cab\ folder also needs to be added to the cab.
3) Last, but extremely important, set the install dir to \CHTAddons\^widgetName^ - where ^widgetName^ should be your unique widget name same as in the lua file.
[[ This is really important. If you are not creating a new widget but just editing the mode9 and/or lua files, please do not modify the installation dir in the cab properties, as it is used in the installation process and modification may cause problems in CHT ]]
If you want to test that cab on your device make sure you disable dev mode first ("CHTI.AddonWidgets.DevMode" to 0), so that the dev mode widget you were working on and the newly installed one do not conflict.
A widget must not be installed in both dev mode and as a cab at the same time!
##########################
*** 3) How it works ******
##########################
CHT addons plug into slots that interface with the core layout manager.
There is maximum number of addon slots (that number is 10 for the dev preview beta, but it will be 20 for the final).
Each widget consists of 4 parts:
1) a mode9 file for the CHT widget interface
2) a lua file for the CHT widget interface
3) any number of extra mode9 or lua files
4) xml file with a manila file list for CHTScheduler
Numbers 1-3 there are directly needed for CHT. Number 4 is needed for CHTScheduler (I'll leave the explanation of that for the CHTS thread - it's not need for now if you just want to try to build your own widget).
Numbers 1 and 2 are the most important and they are directly linked to the slots.
Here is how:
The interface mode9 and lua need to have a specific names depending on which slot they go into.
To make this happen those 2 files are dynamically named on install.
While you are developing your widget you are working with the dev widget slot. There is only one of these so it has one pair of mode9/lua names (30182CB6_manila and 7D241726_manila).
But once you make the addon cab the widget can be installed in any slot (first one found to be free). That's why in the release files, there is a CHTmode9_manila and CHTlua_manila.
Those are the same files that you were developing with (30182CB6_manila and 7D241726_manila) - they will be renamed on the fly once installed - this is where the special setup.dll comes in.
The dll will look for the first free addon slot and install the widget there, i.e. it will rename the files so they correspond to the first slot.
The install dir name that you had to specifically enter is used as the widget install ID and will be stored in HKCU\Software\HTC\Manila\ "CHTI.AddonWidgets.SlotX" (this is needed to uninstall the widget correctly).
The files that are being installed should all go to \windows so you set that directly for the files, and that allows the install dir name cab field to be used for this purpose.
Click to expand...
Click to collapse
If you have reached here I recomend you re-read Co0kie's guide, is short but it contains a lot of information, i would say every word is important!
So now the first trial:
1.- Install the kitchen: Every widget has its own kitchen, I have attached a kitchen for a very simple widget. Just download in your PC and copy all the files & folders in a separate folder (\CHTwidgets\PoyTEST\) same as they are inside the .rar
Now connect your PC and your device via USB and sinchronize. Then run the file z_init.bat - You need to run this one before starting. You just need to run it only one time. It will copy restartmanila.exe to you device.
2.- Put your device in DevMode: Go to HKCU\Software\HTC\Manila\CHTI.AddonWidgets.DevMode and change to DWORD =1 (create if does not exit). Now restart Sense.
3.- Run the file _Deploy_to_device_in_dev_mode.bat. Your device will automatically restart Sense. Then go to Edit Mode - Add new element - Select PoyTEST - done. You should see now the simple widget in your device's screen.
It will continue ....
SENSE CRASHED? NO PANIC
It is normal to crash sense when you are doing some experiments, but it normally get solved just deleting files 30182CB6_manila & 7D241726_manila in \windows folder\ and/or dissabling DevMode in registry HKCU\Software\HTC\Manila\CHTI.AddonWidgets.DevMode = 0
rat_2665 said:
It's a tricky thing. Do you use one of Co0kies widgets? For this I "took it over" at first. I didn't change the structure, only made new names in the manila files. You have to check over and over. A blank space in a name in the mode9 file cost me a day. In the next step you can try to change the behaviour.
What you see is the normal screen for an error (i had it often ). Check if all variables in the lua files are also in the mode9 file. Then in the developer mode you can't see errors in the lua scripts (absent end in functions and so on). For this I used sometimes the m9editor, compiled the scripts and looked for errors.
Click to expand...
Click to collapse
Even we can learn from this crashs:
Co0kie Monster said:
Sense nuke and lua "debugging"
The empty screen after adding your widget will happen if there is an error in your widgets lua code. Alternatively it could be a bug in the mode9 file (but those usually cause sense not to start at all), or maybe you left dev mode on and installed your widget via cab - dev mode uses a special widget slot and it will cause a conflict if a widget is installed both via cab and in dev mode at the same time, so remember to turn off dev mode.
But, anyway I'm guessing the problem would usually be in the lua code. In that case you need to debug it. I've uploaded all the needed tools to "Co0kie's Home Tab\_Development\Lua_debugging_tools". (* inlcuded in the widget kitchen)
Because lua is a script It's not really debugging, it's pretty much just a trace log.
Run attach.bat while your device is connected via active sync and that will collect trace information and display any errors along with the file and line where they occurred.
All the info is collected in debug-attached.txt.
Do whatever causes the bug, then run terminate.bat to stop pdebug (that will also restart manila).
Open up the log and look for **Lua Error******.
Other than that you will also see trace() output there.
The other batch (run.bat) is for debugging from startup. You need to turn off manila (WM Settings->Home-> turn off HTC Sense from the list) and then hit run.bat - it will start manila and log at the same time. That's only needed in case of startup errors.
Click to expand...
Click to collapse
HOW TO SOLVE SOME GRAPHICS ISSUES
santod040 about some graphic issues said:
I am not exactly sure yet why the 16 rule only applies to some roms. I think this may actually be the difference between a CFC and non CFC manila.
Though Im digging into this more still.
I also think of this more as one rom listening to the mode9, no matter what the image claims to be or is.
Where the other needs the image to specifically be what it expects, according to the mode9 and lua.
I also think it's more about "4" and "16"
Here's a few key items from Mode9 and a small bit about each.
Though it may be somewhat irrelevant mostly.
String: UTF-16LE encoded strings (represented as UTF-8 in XML and YAML)
Path: UTF-16LE encoded strings (represented as UTF-8 in XML and YAML)
UInt32: 4 byte unsigned integer
Q16: 4 byte Q16.16 fixed point number
Int32: 4 byte signed integer
Boolean: 4 byte, either 1 or 0
Vector3: 3*4 bytes of Q16 numbers (X,Y,Z)
RectQ16: 4*4 bytes Q16 numbers (X,Y,Width,Height)
RectInt: 4*4 bytes of signed integers (X,Y,Width,Height)
Size: 4*2 bytes of Q16 (Width,Height)
Color: 4*1 bytes (R,G,B,A)
Viewport: either a Vector3 or a RectQ16, depends on size
FrameValue: either a Vector3 or a Q16 number, depends on size
BinaryScript: a binary value, encoded as Base64 in the XML or YAML file
The CFC should not be used as a standard.
Heres why:
Non Cfc and Cfc images, will work on a Cfc rom.
Whereas Cfc images will not work right on a non Cfc rom(any stock rom).
So to be universal, non Cfc is the best approach.
Also consider that manila, and your device have to decompress as they use the images.
So, to offer Cfc as an option is nice, but not the universal offering.
Click to expand...
Click to collapse
santod040 said:
Similar issue again.
The qtc needed to be a more accepted dimension by manila.
I still don't have any concrete answers behind it, other then the info I already posted regarding textures and sizes in manila.
So, I adjusted the mode9 and also the qtc to be standard sizes.
I have made a few that worked.
The first was 256x64, but then was hard to move, lol.
So I edited again and made it 512x64 and reposted just now.
It seems to move just fine.
Now only to move the resize button up some and it would be near perfect.
But since it's almost 3am, that will have to wait.
Click to expand...
Click to collapse
santod040 said:
Something else to think about.
As far as the 16 rule.
I also mentioned 4.
So for example,
64 divided by 16 = 4 (good number)
96 divided by 16 = 6 (bad number)
128 divided by 16= 8 (good number)
Click to expand...
Click to collapse
only 10 widget slot problem solution
mike2nl said:
We, the CHT teams, have found a solution for the 10 slots for widget issue.
After we had changed things we are now in state to use 20 widgets(*) at all (0..19).
It is tested on HD2 and TP2 WM phones, and it's running without any issue until now.
The new file was tested by santod040, MichelDiamond, poyensa and me.
My last test was to use 20 widgets on the HD2 about the performance. And yes it does the work .
How to install the fix:
1. unzip the manila file
2. switch off sense
3. copy the 7c60907d_manila file o the \Windows directory
4. restart your phone
5. switch on sense
6. have fun to install more widgets now (max. of 20)
7. follow the install routine from every widget
Click to expand...
Click to collapse
Last but not least, thank you to all involved team members...
Click to expand...
Click to collapse
You can do your own widget just changing PoyTEST - PoyText1 - PoyGraphic1 for your own names
The best way to make a new widget is start from another widget, in this case we can start from PoyTEST, its a simple widget with 2 variables to display in the home screen of our devices: one graphic file as background and one text field. This 2 fields (or variables) will be created by the mode9 file. We have to give unique names for all the variables so the easiest way is just to change PoyTEST - PoyText1 - PoyGraphic1 - for your own names in every line of the files involved. So open file 30182CB6_manila using m9editor and do the changes. (If you are not familiar with m9editro go here)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The mode9 file 30182CB6_manila use to define also the content of the graphic variables (SetTexture) but we will do it later for this example. Other important thing is the order in mode9 stablish the order of the elements shown in ours screen. It means that we will see PoyText1 over PoyGraphic1 as we like.
Now we have to change the file CHTWidgetDev.lua using Notepad2 and change all the PoyTEST - PoyGraphic1 & PoyText1 for the name previously used in the mode9 file. It not dificult just change PoyTEST -nothing else- in every line where it appears, substitute for the name previously used in mode9 file. YES YOU HAVE TO LEAVE THE SMALL w
Some important things:
Be careful with capital and lower letters. For lua languaje 'PoyTEST' is different than 'poyTEST' so only one letter can make the widget not working.
If the line strat with '--' then the line is dissabled, this is usefull for notes & reminders and also to activate and deactivate lines. If you use Notepad2 the deactivated line will be green coloured.
The files 30182CB6_manila (mode9) & CHTWidgetDev.lua always have to be in any CHTwidget, and they must have always the same structure. In mode9 file 30182CB6_manila we do create the variables and in CHTWidgetDev.lua (renamed as CHTlua_manila in the cab) we connect the widget to the rest of Co0kie Home Tab.
Now we do not need to change anything, may be later when we are more familiar with widgets:
* Lines 3-8 is to register the widget in CHT
* Line 8 is connected to line 82-83-84. We define there how many layouts is going to have the widget (black-white-etc). We leave everything as it is now ...
* Lines 10-48 are to control the size of the widget, in the future you can play there a bit specially in line 42 if you wish your widget bigger, but now we leave it as it is.
* Lines 50-62 are very important. We do nothing there -never- just change the names for our's widget name. Specially line 62 we put there the object (clockface, bakcground, etc) that is going to react when we press it with our finger. In our case it will be PoyGraphic1 (change it for the variable name used in mode9 file 30182CB6_manila).
* Line 64 conect to our widget lua file. As you may know the lua file defines the behaviour of the widget. In this lua file we are going to say what our widget is going to do. Is time to open ManilaHash and find the manila name of our widget's lua file. Dont change the path just the final name, you can use any but by convention better use something like CreatorName_WidgetName.lua
* Lines 82-84 is to add more layouts in our widget. You can see some examples in other widgets and also in CHT_Widgets.lua (CHT source), but dont forget to modify line 8 then!
* Lines 88-104 is defined the animation effect how the widget comes to the screen when swipping between levels. I never touch anything there.
* same for lines 106-116. It was there before me and i never modify anything there (just the widget name)
* Now have a look again to every line, check the spelling, capital letters, etc.
Now you are using manilaHash you can also find the name for any other graphic file you are going to use. e. Dont change the path just the final name
Now we can start to modify the file PoyTEST.lua. Using Notepad2 you have to change PoyTEST for your widget name used in the previous lua file and also modify the name of the variables defined in the mode9 file 30182CB6_manila (PoyText1 & PoyGraphic1) in all the lines where those appears.
In this lua file can be added some properties that use to be set in mode9 file (lines 15-25) I do that for one reason: This file does not change the name in the widget installation process, as the other CHT files (CHTmode9_manila & CHTlua_manila) does. This file will be always 41CBC6DC_manila in \windows\ folder so it is easy to substitute later to correct some bugs, etc.
You can get out of the line 29 (just put -- at the begining of the line it will be green cloured) This is a test I am doing for translate widgets regarding this post. If so you have also to activate the line 28 (delete -- then the line will be black colour) and delete file PoyTESTtranslation.lua in \PoyTEST\workspace\_lua
I cannot say much more for this file. Here comes the problems. How to do things? I am not a coder I have only read and read and read a lot of code in other widgets and CHT_Widgets.lua and other files in CHT source, and try and try and try a lot, and finally ask rat_2665
* Line 33 is a way to set texture for graphic fields in lua files instead of mode9 files
* Lines 38-63 is to define what the widget does when pressed
You can do your own widget just changing PoyTEST - PoyText1 - PoyGraphic1 for your own names
Now is time to check the USB conection, device is sinchronized, then click on _Deploy_to_device_in_dev_mode.bat and see your widget working!
[[be sure the .bat file has been edited correctly by adding your widget name, as explained in post#8]]
Sense crashed ... dont worry. Nobody has got it at the first time!
1. Be sure you are in DevMode
2. Check that all the names are correctly written, specially capital letters- lower letters
3. if you got an error in the black screen after run .bat file, read it slowly. It will help
4. Once you make the corrections you can run again .bat, even with sense crashed.
MAKING THE CAB
Co0kie Monster said:
When you have finished making your widget, you can pack it up into a cab file.
To prepare the files for the cab you have to run "_Generate_files_for_cab.bat".
The final files will be in the \cab\_files_final\ folder.
Making the cab file - this is what an addon cab must have:
1) Every last one of those files from \cab\_files_final\ need to be in the cab and they have to be set to be copied to %windows%.
Do NOT set the install dir to %windows%, set the files to be copied to %windows%.
2) The setup.dll that is in the \cab\ folder also needs to be added to the cab.
3) Last, but extremely important, set the install dir to \CHTAddons\^widgetName^ - where ^widgetName^ should be your unique widget name same as in the lua file.
Click to expand...
Click to collapse
Be sure that you have edited the file _Generate_files_for_cab.bat with your own name widget as explained in post#8. By running this file all the lua files will be recompiled automatically and all the files will go from \workspace\ to \cab\_final_files\ If you have a look to the screenshot you will notice that some files names have changed: we will find there CHTlua_manila & CHTmode9_manila. This 2 files will change the name again when the cab be installed in the device, depending the free slot asigned will take the final manila in \windows\ folder in your device. Isn't magic?
Dont forget to add the magic setup.dll. When you add the files into the cab select windows as location. Then in cabinet properties - Installation directory do create a folder in \root\CHTAddons\NameOfTheWidget with the same name as your widget (line 5 of chtwidgetdev.lua) and mark hard-coded-path. Finally save the cab.
CHTScheduler
If we add a xml file named as CHTWidget_NameOfYourWidget.xml (CHTWidget_PoyTEST.xml in this case) directly in \windows\ folder with just a description of the manila files names used in our widget (see some of them as example) this widget will be used by CHTSheduler for diferents profiles, baselines, etc.
It does not seems dificult, isnt it? it simple but if you substitute the qtc file attached 1F88A376_manila, and change the color property for the text in line 17 of PoyTEST.lua to black (0,0,0,255) .... it could be the begining of an usefull widget
1.- Lets do our own CHTwidget
2.- Using JMLMenuSense
3.- Final touches
4.- A Bit of CHTS
Its good to have a look into CHTWidgetDev.lua from Co0kie's Standalone Analog Clock, with extended comments by Co0kie (in green). You have it into the Co0kie's widgets kitchen. We all started here:
-- File name: 7D241726_manila -- \windows\htc\home\scripts\home\chtwidgetdev.luac
-- ##### CHT Wigdet interface file #####
-- this script is an abstraction layer that sits between a widget and the core CHT Layout Manager
-- the template needs to be filled in the correct way, but once it is, the created widget will be plugged into the layout manager
-- and automatically behave like any other CHT widget - be movable, have access to different layout profiles, correct lockscreen behaviour etc.
-- even if I do say so myself, the system is *very* powerful
-- the comments below should provide a good description of the template
-- the primary and most important comments will be marked plainly with --
-- secondary comments will be marked with --// and they will contain some additionl points of interest, but not critical info
-- on your first read through I suggest you stick to just the primary comments
-- lines marked with --%% are commented out code that could be part of a template, but is not needed for this example in particular
-- if you have any other question, hit me in the social group
-- this first line creates a new template file based on 'WidgetTemplate' (defined originally in CHT_core.lua)
--// it's best to make it a local - it can be a global too, but there's really no need since it will not be accessed directly anywhere
--// except in this file - and one less global means less polution in the global namespace which could be very important going forward
local wStandaloneAnalogClock = WidgetTemplate:new()
-- this next step registers the newly created widget with the core CHT Layout Manager
CHTLayoutManager:RegisterWidget(wStandaloneAnalogClock)
-- some basic information needs to be filed in about the widget
-- 'widgetName' field - try to make this name as unique as possible, because it is used to save/load widget registy information
-- the core widgets have plain names (Clock, Appointments, Tasks...), but give your widget unique names to avoid conflicts
-- the simplest unique naming scheme would be to just add your name before the widget name
wStandaloneAnalogClock.widgetName = "Co0kieStandaloneAnalogClock"
-- this defines the text that will appear in the advanced settings/add a widget menu
--// sadly, I could not find a way to make the localization system distributed for every widget so you can't enter localized "IDS_*" strings here
wStandaloneAnalogClock.settingsString = "Standalone analog clock"
-- this defines the category in which the widget will appear in the advanced settings/add a widget menu
wStandaloneAnalogClock.settingsCategory = "Clock"
-- the maximum layout count (the layouts that are cycled by the previous/next button on the popup menu or in the settings menu combo box)
wStandaloneAnalogClock.layoutCount = 1
-- should the widget snap to the center of a page
-- // but "center" isn't really center - it's more like snap to posX == 0, 480, 960..., if that position X is the center of a page depends on how you made your widget
wStandaloneAnalogClock.snapToCenterX = false
-- here you can define default settings for your widget on a "per layout" basis
-- if defaults for a level are not given, it will use {visible = false, layout = 0, posX = 0, posY = 0, scale = 1, pinned = false}
-- the visible, posX and posY fields speak for themselves
-- the layout field is the layout number (can be between 0 and layoutCount-1)
--// scale is used for storing size info for resizable widgets
--// pinned is used for storing the pinned state of pinnable widgets
--%% wStandaloneAnalogClock.defaults["HomeLevel0"] =
wStandaloneAnalogClock.defaults["HomeLevel1"] = {visible = false, layout = 0, posX = 0, posY = 0, scale = 1, pinned = false}
--%% wStandaloneAnalogClock.defaults["HomeLevel2"] =
--%% wStandaloneAnalogClock.defaults["HomeLevel3"] =
--%% wStandaloneAnalogClock.defaults["HomeLandscape"] =
--%% wStandaloneAnalogClock.defaults["CHTLockscreen"] =
-- now come the widget function definitions
-- 'Initialize' - and extremely important function
-- it's called when the widget it loaded for the first time (on startup or when added from the advanced menu)
wStandaloneAnalogClock.Initialize = function(self)
-- these first few lines should be the same for all addon widgets
local newComponent = Component()
WidgetLayer2D:Attach(newComponent) -- you may modify this to be either WidgetLayer2D or WidgetLayer3D -- more info on this later
if not self.addonWidgetID then -- this is very important, every addon widget must have these line - do not modify them
newComponent:SetComponentClipCharacter("CHTWidgetDevSlot")
else
newComponent:SetComponentClipCharacter("CHTWidgetSlot" .. tostring(self.addonWidgetID))
end
self.positionLayer = newComponent
-- these two need to be filled in but they differ depending on how you named your mode9 fields
self.animationLayer = StandaloneAnalogClockAnimationLayer -- the layer that will be animated (fade in/out or any other more interesting effect that you can define - dee below)
self:AddObject(SACFace) -- defines the touch surface that, when touched, will enable the widget to be moved
-- the rest is completely up to you
require("Home\\Scripts\\Home\\Co0kieAnalogClock2") -- the script file that describes the behaviour
-- make sure that all new names that you add are unique so that there are no conflict with built-in widgets or any other addon widgets
-- suggested naming scheme is: yourname_variablename
-- the unique name requirement goes for all objectc in mode9 files, lua global variables and classes
StandaloneAnalogClock = StandaloneAnalogClockClass(StandaloneAnalogClockGroup, SACFace, SACMinuteHand, SACHourHand, SACSecondHand)
end
wStandaloneAnalogClock.GetPosX = function(self)
return self.posX + 128 * (1 - self.scale)
end
wStandaloneAnalogClock.GetPosY = function(self)
return self.posY - 128 * (1 - self.scale)
end
-- GetHeight and GetWidth provide feedback for layout manager so it can know the exact borders of a widget
wStandaloneAnalogClock.GetHeight = function(self)
return 256 * self.scale -- in this the base width of the analog clock is muliplied by the scale
end
wStandaloneAnalogClock.GetWidth = function(self)
return 256 * self.scale
end
-- resizing system definitions - I suggest you skip this part on your first read
wStandaloneAnalogClock.isResizable = true
wStandaloneAnalogClock.rotatingResizeButton = true
wStandaloneAnalogClock.GetResizeRefX = function(self)
return self.posX + 128
end
wStandaloneAnalogClock.GetResizeRefY = function(self)
return self.posY - 128
end
wStandaloneAnalogClock.GetResizeButtonXDelta = function(self)
return 90
end
wStandaloneAnalogClock.GetResizeButtonYDelta = function(self)
return -90
end
wStandaloneAnalogClock.CheckScaleLimit = function(self, scale)
return (scale >= 0.5 and scale <= 1.3), 0.5, 1.3
end
wStandaloneAnalogClock.GetResizeUnit = function(self)
return 128
end
wStandaloneAnalogClock.ApplyScale = function(self, newScale)
self.scale = newScale
local newRadius = self:GetResizeUnit() * newScale
self.animationLayer.Scale = Vector3Property(Vector3(newScale, newScale, newScale))
end
-- these are the layout control functions
-- this example widget has only one layout available, but these function come in very handy for defining multiple layouts
-- this function is run before any of the defined layout functions
-- this should contain something that should be set commonly for any layout
wStandaloneAnalogClock.CommonPreSetLayout = function(self)
StandaloneAnalogClockAnimationLayer.Center.x = SACFace.Size.width / 2
StandaloneAnalogClockAnimationLayer.Center.y = -SACFace.Size.height / 2
if not self:CheckScaleLimit(self.scale) then
self.scale = 1
end
self:ApplyScale(self.scale)
end
-- one of these functions is run depending on the selected layout
-- the string to be shown in the settings menu combo box is also defined here
wStandaloneAnalogClock.layoutName[0] = "[[IDS_NO_ALT_LAYOUTS]]" -- combo box text
wStandaloneAnalogClock.SetLayout[0] = function()
end
-- additional layouts can be defined here
-- the number of functions must match the layoutCount field defined above
--%%wStandaloneAnalogClock.layoutName[1] = "Second layout"
--%%wStandaloneAnalogClock.SetLayout[1] = function()
--%%end
--%%wStandaloneAnalogClock.layoutName[2] = "Third layout"
--%%wStandaloneAnalogClock.SetLayout[2] = function()
--%%end
--%%wStandaloneAnalogClock.layoutName[3] = "Etc"
--%%wStandaloneAnalogClock.SetLayout[3] = function()
--%%end
-- like CommonPreSetLayout this function is run for any of the layouts
-- but it's run after the layout specific function
--%%wStandaloneAnalogClock.CommonPostSetLayout = function(self)
--%%end
-- animation function, they are run when switching between level or adding/removing a widget
-- the basic thing that needs to be done here is make the widget visible or invisible,
-- but you can play around with the animations and put in some eye candy
--// Interopolate can be used with Opacity, Position, Rotation and Scale and some cool effect combinations can be made
--// post in the social group if you need more info
wStandaloneAnalogClock.AnimateIn = function(self, instant, swipeDown)
if instant then
self.animationLayer.Opacity.value = 100
else
self.animationLayer.Opacity:Interpolate(100, 10, 0, Interpolate_Linear)
end
end
wStandaloneAnalogClock.AnimateOut = function(self, instant, swipeDown)
if instant then
self.animationLayer.Opacity.value = 0
else
self.animationLayer.Opacity:Interpolate(0, 5, 0, Interpolate_Linear)
end
end
-- these two functions define what should be run to connect or disconnect widget press actions
-- the functions are called on transition to the lockscreen, edit mode, but also for some smaller details (like when menus are up)
wStandaloneAnalogClock.ConnectPressHandlers = function(self)
StandaloneAnalogClock:ConnectPressHandlers()
end
wStandaloneAnalogClock.DisconnectPressHandlers = function(self)
StandaloneAnalogClockisconnectPressHandlers()
end
-- these two do much the same as the previous functions, but the serve as exceptions for the lockscreen
-- in this case the analog clock should not have any action on the lockscreen
-- but for example, the music player uses these functions to reconnect the play controls on the lockscreen
--%%wStandaloneAnalogClock.ConnectLockscreenHandlers = function(self)
--%%end
--%%wStandaloneAnalogClock.ConnectLockscreenHandlers = function(self)
--%%end
-- this one is used to clear the the widgets selection status
-- in this example when the clock is pressed it sinks in a bit
-- in certain situations, there might be a need to deselect a widget even if it's still under the finger
-- (for example when a side scroll is started)
-- that's when this function is called
wStandaloneAnalogClock.ClearSelection = function(self)
StandaloneAnalogClock:ClearSelection()
end
Click to expand...
Click to collapse
You can try now making your own Clock-CHTWidget, following rat_2665 tutorial:
This is a little guide for clock widgets:
Read at first the widget development guide by Cokie (it's in the below mentioned kitchen) !!!
Step 1 manila hash names
1. Download the kitchen for the analog clock widget by cookie and make a temp folder in there. Copy the files for your analog clock in this folder (best if you have already a working clock for CHT 1.8.5). Save the pictures out of the qtc manila files as png in this folder (this is only useful for oversight). Rename the whole widget with your widget name.
2. Make a list with new names for your text and image objects with manilaHASH.
- the names should be unique. I use my name and a widget number as prefix, f.e. rat_w001_secondHand
- determine the manila hash name. For this use the line
\windows\htc\home\assets\images\Home\VGA\Your_Name.qtc
Save this list. You need it all the time for oversight.
3. Rename your images in the temp directory with the new manila names (this is only useful for oversight); then rename also your manila image files with these names.
4. Delete all files in the workspace\qtc directory and copy your new manila files into this (but not the old 1E1A6CCD_manila and 1EC5924B_manila)
Step 2 mode9 file.
5. Open the mode9 file in the workspace directory. Go in the library to the StandaloneAnalogclockGroup. There are the image and text objects for the clock.
6. If you have more objects in your old 1E1A6CCD_manila file for your analog clock add these objects in the group.
7. Then substitute
- for all objects the Instance value with your new name (f.e. rat_w001_secondHand),
- for the image objects the Texture path with the (here shortend) string that you used for the manila hash name (f.e. .\Assets\Images\Home\VGA\rat_w001_secondHand.qtc)
- for the text objects the String value to the variable used in the lua file (f.e. rat_w001_weekday). If you want to use AMPM like in the normal clock, don't change this value.
8. Change the name of the StandaloneAnalogClockGroup to a unique name (that is used later in the lua files, f.e. rat_w001_ClockGroup)
9. Change the name of the StandaloneAnalogClockAnimationLayer to a unique name (that is used later in the lua files, f.e. rat_w001_ClockAnimationLayer)
10. Save the file.
Now to the lua files.
Step 3 CHTWidgetDev
Substitute all uses of wAnalogClock2 with a unique name (f.e. w_rat_w001_Clock). You can do this in Notepad2 with the Edit/Replace function.
Then substitute in line 69 StandaloneAnalogClockAnimationLayer with the new unique name you used in the mode9 file for the animation layer (f.e. rat_w001_ClockAnimationLayer).
Do the same in line 74, 135, 136, 191, 195 and 212 for all uses of StandaloneAnalogClock (f.e. rat_w001_Clock)
Replace the string in line 28 with the name of your widget (f.e. "rat_w001_clock").
In the next line insert the string that is shown for the widget in the home layout (f.e. "my analog clock").
For an analog clock you don't need to change the next item (""Clock").
In line 70, 135 and 136 is the image object for touching mentioned. You have to substitute "SACFace" with your image object (at best the greatest, f.e. rat_w001_clockface)
The last part is line 73 and 74. In line 73 you have to substitute "Co0kieAnalogClock2" with the name of your special lua script (f.e. rat_w001_clock).
Line 74 is the bridge to your lua script. Here are the arguments of the ClockClass defined that are used in the StandaloneAnalogClockClass.__init function in your special lua file. Of course the name of the function is later also to be changed.
In the example it is:
rat_w001_Clock = rat_w001_ClockClass(rat_w001_ClockGroup, rat_w001_clockface, rat_w001_minuteHand, rat_w001_hourHand, rat_w001_secondHand)
Step 4 special lua file
For naming use the lua script file name you used in the CHTWidgetDev.lua file (rat_w001_clock)
In the first (commentary) line change the location with the new name instead of Co0kieAnalogClock2 and use the manilaHash app with this string:
\windows\htc\home\scripts\home\your_widget_name.luac
Then substitute also the manila name (f.e. -- File name: 1F2E1A7D_manila --\windows\htc\home\scripts\home\rat_w001_Clock.luac )
Substitute all uses of StandaloneAnalogClock with your name (rat_w001_Clock)
Change all uses of SACShowAMPM to your name (rat_w001_ShowAMPM).
That would be all if you only want to make a normal analog clock widget, but if you want to change more you have to go to the central function for the behaviour. For this you have to look in this two functions (these are the old Co0kie names):
StandaloneAnalogClockClass.UpdateTime = function(self)
StandaloneAnalogClockClass.UpdateSecondHand = function(self)
Here the update interval and the rotation of the hands is defined. In Co0kies clock it is pretty simple. If you want to add more functions here is the place. The names of the standard arguments clockGroup, clockFace, minHand, hourHand and secondHand should be unchanged in the whole file. For every other variable and object use your special unique name.
Of course you can add other functions in their own place. You find examples for this in my clock thread.
Now it is testing, testing, testing.
Step 5 bat.files
In the kitchen there are these two files
_Deploy_to_device_in_dev_mode.bat
_Generate_files_for_cab.bat
for handling in the development process.
Here you have to substitute in both files in the second luatool line 35E966AF_manila ..\Workspace\_lua\Co0kieAnalogClock2.lua
with your new widget name and its manila hash name. (in the example: 4C0089BA_manila ..\Workspace\_lua\rat_w001_Clock.lua)
Step 6 CHTS file
Rename the file in the CHTS with your new widget name (f.e. CHTWidget_rat_w001_Clock.xml).
Open the file with the windows editor.
Take your list with the manila hash names and substitute the objects with your new names and the manila names.
For the third line use your widget name and in the fourth line ("description") the string you used in the CHTWidgetDev.lua for the home layout description.
Click to expand...
Click to collapse
This links always useful ...
TUT: Editing manila!
LuaTool 1.2 - Lua Decompiler, Compiler and Compare
TF3D manila mode9 editor
CFC GUI - THE Manila/TF3D Image Editor
Manila file names
Manila CMD Kitchen Environment
Lua 5.1 Reference Manual
Manila Development for Beginners
Example of use of longpress thanks to RoryB
Modifications of the lua script/functions thanks to rat_2665
and reserved5 (i hope is enough )
Great post...I have been wanting to work on my own widget for CHT. Hope this thread will help me jump start...
So here are a few little things I have gathered over the last few months which I have found useful.
The ManilaHash.txt contains two lines of text for you to cut and paste into Manila Hash which you need to generate the correct manila filenames for your widget scripts and qtc image files. Just open Manila Hash, open the txt, copy and paste the relevant line into MH and alter the last bit to your image/script name. Then click Get Manila and you'll have your unique manila filename. Then highlight the hashed name, right click and copy. If it is the name for your widget script you are generating you then need to use this in the two bat files (Deploy to device in dev mode/Generate files for cab) before you run either bat - right click and Edit and you'll see something like this:
Code:
@echo off
pushd tools
luatool /c -o ..\deploy\7D241726_manila ..\Workspace\_lua\chtwidgetdev.lua
luatool /c -o ..\deploy\3DFA729F_manila ..\Workspace\_lua\dunchexclock.lua
copy ..\Workspace\mode9\*.* ..\deploy >nul
copy ..\Workspace\qtc\*.* ..\deploy >nul
copy ..\Workspace\png\*.* ..\deploy >nul
copy ..\Workspace\locales\*.* ..\deploy >nul
copy ..\Workspace\CHTS\*.* ..\deploy >nul
rapicopy -d -e -s ..\deploy \windows
rapistart restartmanila.exe
del /q /s ..\deploy\*.* >nul
pause
NB - The bat files included in the widget kitchen contain notation by co0kie but the code above shows the actual active parts of the bat.
The line you need to change is this one:
Code:
luatool /c -o ..\deploy\3DFA729F_manila ..\Workspace\_lua\dunchexclock.lua
Change the manila name to the one you just generated for the script (highlight/paste from MH) and change the script name to whatever name you are giving your widget script. BTW confusing as it may seem the hashed name is generated using .luac and the bat refers to it as .lua - this is correct!
Also for reference you should also edit the first line in your widget script to show the correct script name and hashed manila filename. Incidentally you'll notice this line in the script has -- at the start. This basically 'disables' the line so it becomes for reference only. This is handy during testing because you can remove elements from use without actually removing the text from the script, so they are easy to add back in later. If you are using Notepad2 which is in the tools folder (and I strongly recommend you do because it is specifically formatted for editing these scripts) you'll see that lines beginning with -- appear in green so you can easily identify inactive lines.
If you have generated a hashed name for a qtc file then simply copy the name, right click on your qtc file and Rename, highlight current filename and paste.
Widget mode9 Filenames.txt contains the hashed filenames for the mode9 files of each widget depending on which widget slot it is installed into. The mode9 and WidgetDev.lua filenames are generated during install depending on the slot number so you will need these if you are going to edit the mode9 after you have actually installed a widget (not relevant if you are still working on it in dev mode). You can also use this list to locate the mode9 file for any widgets you already have installed but which you may want to take a look at for reference or edit.
LUA Ref v5.1.pdf is a really useful quick reference guide for lua syntax, but before you get in a spin trying to get your head around lua for the first time I would strongly recommend reading this BEGINNERS GUIDE. There are many online references including the main LUA Reference Manual (there's a link to it in the site I've just linked to) but this one gives an easy to follow guide to the basics so read it first!
rat_2665's CHTAddon Dev Mode Switch - adds a new toggle switch in the CHT Toggle Switches list. Works like every other toggle to activate/deactivate Dev Mode rather than having to do it manually with a registry editor. Just toggle on/off and soft reset after each change to enter/leave Dev Mode. I'm sure rat won't mind me posting this here - it's all his work so all credit to him for this one - but it really is a timesaver when you are developing!
One final word of advice/experience - when you are first starting out on developing widgets it can be very VERY frustrating, especially if like me you have absolutely no previous experience of coding. However we are all here to help -that's what this community is all about. If you have a problem just ask. And be prepared for many many Sense crashes and resets! But hey, that's what dev mode is there for - another of co0kies little flashes of genius!
Right, that's just to give you all a hand with some basics! We are now open for business - ASK AWAY
Thanks Poy, Rat, Dunc, and all those involved with CHT and CHT widget dev.
This could prove to be very useful for anyone wanting to jump into making their own widgets and for collaborative efforts as well.
I look forward to seeing where this goes from here.
If I decide to add anything to the great info already posted, I will place it here.
Thanks for your efforts to get this going Poyensa.
Excellent thread, hope to try out the tutorial at some point.
At the moment interested in the toggle switches and how to make them, since it's not covered anywhere.
I've opened up rat_2665's toggle switch cab (hopefully that is ok - it is a good example).
The two key files are:
CHT_switch_DevMode.png
CHTlua_manila
The lua code is as follows:
Code:
Co0kieSwitchLink("DevMode Switch", "\\Windows\\CHT_switch_DevMode.png", _application.Store:GetValueChangedEvent(Lifetime_Permanent, "CHTI.AddonWidgets.DevMode"), function(l_1_0)
if _application.Store:GetIntValue(Lifetime_Permanent, "CHTI.AddonWidgets.DevMode") == 0 then
_application.Store:SetIntValue(Lifetime_Permanent, "CHTI.AddonWidgets.DevMode", 1)
else
_application.Store:SetIntValue(Lifetime_Permanent, "CHTI.AddonWidgets.DevMode", 0)
end
end
, function(l_2_0)
if _application.Store:GetIntValue(Lifetime_Permanent, "CHTI.AddonWidgets.DevMode") == 0 then
return false
else
return true
end
end
)
From the above you can identify:
The switch title - "DevMode Switch"
The graphic - "\\Windows\\CHT_switch_DevMode.png"
Trigger - _application.Store:GetValueChangedEvent(Lifetime_Permanent, "CHTI.AddonWidgets.DevMode")
Action - function(l_1_0)
Switch position - function(l_2_0)
The setup.dll in the cab, sorts out the install side (as mentioned in the other posts).
Anyone know what lua file is the wifi switch? Or what regkey it monitors? Thanks.
Sorry if this info is written somewhere else, but I've not been able to find it so far.
meltwater said:
Anyone know what lua file is the wifi switch? Or what regkey it monitors? Thanks.
Sorry if this info is written somewhere else, but I've not been able to find it so far.
Click to expand...
Click to collapse
I would like to know that as well.
ai6908 said:
I would like to know that as well.
Click to expand...
Click to collapse
The wifi switch is in the Co0kieLink.lua file
Code:
Co0kieSwitchLink("[[IDS_WIFI_TOGGLE]]", "\\Windows\\CHT_switch_wifi.png", machineStatus.WifiOn.OnValueChanged
,function()
JMLComm("wifi")
end
,function()
return machineStatus.WifiOn.Value
end)
meltwater said:
Anyone know what lua file is the wifi switch? Or what regkey it monitors? Thanks.
Sorry if this info is written somewhere else, but I've not been able to find it so far.
Click to expand...
Click to collapse
ai6908 said:
I would like to know that as well.
Click to expand...
Click to collapse
Download CHT_AddonLinksKitchen.zip in post#6 of CHT2.0 thread. Inside \workspace\_lua\ you will find decompiled 6ADCC943_manila -- \windows\htc\home\scripts\home\chtlinksdev.luac with comments from co0kie
You beat me to it! BTW, Meltwater in the house - we are honoured
Making new links is actually way easier than making new widgets because there are only very small scripts involved and no mode9. You can either make new links to add in to the existing link sets (Miscellaneous, Toggles, etc) which is really straightforward, or you can create entirely new link sets. I have done both, adding new DatePicker and All People links into the Misc group, and making the new Page Switch Link set. Making a new set is also pretty straightforward although you also have to define the class and function, but most importantly each new set of links must have a unique link ID. This ID needs to be chosen and then notified to the CHT dev group in the Widgets discussion. If you don't have access to it then ask here and we'll provide you with one and feed it back to the dev group.
I can't remember what's in the kitchen Poy just linked to so I have attached my three kitchens below, along with a zip containing the CHT_quicklinks and freelinks luas and one of MichelDiamond's scripts for some of the links he added in for CHTS.
Again, any questions you have keep asking. We're waiting to see what amazing new stuff you come up with...
Dunc001 said:
You beat me to it! BTW, Meltwater in the house - we are honoured
Making new links is actually way easier than making new widgets because there are only very small scripts involved and no mode9.
... ...
Again, any questions you have keep asking. We're waiting to see what amazing new stuff you come up with...
Click to expand...
Click to collapse
Thanks guys. I did look at this when it was released, but found it difficult to get started with it.
That was my theory, make a few switches and get used to the plugins. Thought I could make some custom ones for switching on an in-car mode and various other things (switching into development modes for debugging the tabs would be handy too).
Obviously there is potential for using the stuff I've got for an improved RSSWidget and FbWidget but I'm still working out how to create stuff from scratch (but I am getting there).
Would be interesting to make a widget which displays set text items (perhaps a graphic too) from the registry, with callbacks to an app if pressed. That would be enough for a .net program to tie into, this is the basis of the RSSTab. Such a general widget could be used for a lot of things.
By the way, if you want to use some wiki space, feel free to carve out a chunk!
http://forum.xda-developers.com/wiki/index.php?title=WM6_HTC_Sense_Developer_Wiki
Have you got the CHT RSS widget kitchen? I'll upload it if not. If you could make a widget template for an updated rss widget or Facebook/Twitter widget to look/function in a similar way to the Android sense widgets that would be fantastic. Scrollable, with channel icon/Facebook pic beside each item, and also showing update time. Core CHT tasks and contacts widgets are already scrollable so all the necessary code should be available to copy/adapt. Let us know what you need any help with.
Dunc001 said:
Have you got the CHT RSS widget kitchen? I'll upload it if not. If you could make a widget template for an updated rss widget or Facebook/Twitter widget to look/function in a similar way to the Android sense widgets that would be fantastic. Scrollable, with channel icon/Facebook pic beside each item, and also showing update time. Core CHT tasks and contacts widgets are already scrollable so all the necessary code should be available to copy/adapt. Let us know what you need any help with.
Click to expand...
Click to collapse
I think I'll get my feet wet by doing some toggle switches first.
At the moment don't have the time to do the full widgets yet, got plenty that needs doing on the tab itself, but it would be great to get it all to tie in.
Well, the basics are done. If you miss something let us know. We also will try to bring here some tricks, fixes, mods, etc. And of course the answers for all your questions, excepting the date for next CHT update!
meltwater said:
Would be interesting to make a widget which displays set text items (perhaps a graphic too) from the registry, with callbacks to an app if pressed. That would be enough for a .net program to tie into, this is the basis of the RSSTab. Such a general widget could be used for a lot of things.
Click to expand...
Click to collapse
I totally agree with you.
I am monitoring this thread since its creation and I plan to investigate it when I will have more free time next week.
My goal: modify the RSSWidget to display feed informations from Google Reader (via the "Speeed Reader" application and probably a mortscript to parse the .xml and update registry).
kalhimeo said:
I totally agree with you.
I am monitoring this thread since its creation and I plan to investigate it when I will have more free time next week.
My goal: modify the RSSWidget to display feed informations from Google Reader (via the "Speeed Reader" application and probably a mortscript to parse the .xml and update registry).
Click to expand...
Click to collapse
Well I hope to integrate Google Reader into the RSSTab at some point.
Touchwizz 4.5 NextGen : little "HowTo"
Hello everybody.
I started this thread to put all informations, tips'n tricks and howto for a best use of this very cool launcher "TW 4.5 NextGen" made by fr4gg0r. Note that I will try to add your tips as soon as you deliver them here.
First at all, the link to the concerned thread of this launcher :
>> http://forum.xda-developers.com/showthread.php?t=1061883
Note that you will not find in this subject the download of files. Please refer to the link and thread above.
This HowTo is so subdivised :
Installation of Applications & Widgets
details about installation of what you need to have, to do for having this launcher.
>> see here : http://forum.xda-developers.com/showpost.php?p=18491540&postcount=2
Use of TW4Manager
how to use it, in quick words. This programm is intended to download the latests versions and the themes :
a. select, download and apply Themes (as they are shared by fr4gg0r)
b. select, download and apply Widgets signed (as they are shared by fr4gg0r)
c. see tutorials (links in version #6 not functionnal)
d. verify your donation (as they are updated by fr4gg0r)
e. check for updates of tw4manager and tw4.5 launcher, uninstall, see changelog,...
Launcher TW4.5 : supported phones
a little list, maybe not so exhaustive of supported phones, normally every device with armv7 processor and froyo or higher.
Launcher TW4.5 : installation problems
how to bypass installations problems? Many suggestions and maybe (certainly) solutions !
>> see here : http://forum.xda-developers.com/showpost.php?p=18491546&postcount=3
Launcher TW4.5 : resigning widgets
To fix non-working widgets :
grab the key attached in the officiel thread
decompile with apktool.
open AndroidManifest.xml
edit the sharedUserId so (if not there add it) :
Code:
android:sharedUserId="tw4.fr4gg0r"
recompile
use jarsigner from android sdk to resign with the key (password is touchwiz, alias is fr4gg0r) :
Code:
"[java -jar] jarsigner -keystore /...tw4key -storepass touchwiz theWidget.apk fr4gg0r
Official details are here.
Launcher TW4.5 : actions on screens
details on how to change the size of widgets, add new shortcuts, set default screen, change wallpaper,...
>> see here : http://forum.xda-developers.com/showpost.php?p=18491550&postcount=4
Launcher TW4.5 : preferences
what let you do what for this launcher.
>> see here : http://forum.xda-developers.com/showpost.php?p=18491553&postcount=5
Launcher TW4.5 : Widgets
quite all about widgets
>> see here : http://forum.xda-developers.com/showpost.php?p=18491562&postcount=7
Launcher TW4.5 : docking icons
how to modify or add icons to the dock bar (bottom bar of the launcher).
>> it's very very simple to add icons to the dock bar. Here you go :
open TW4.5 Launcher preferences to be set the number of icons to be shown :
Dock settings
in "Icon Dock Count" be certain to have more than 1 icon selected.
if "Centered apps icon" is checked, the shortcut to appdrawer will be centered (else not)
make your options or modifications, save and exit
from the mainscreen
bring up the appdrawer from the main screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
press the menu button
select edit (modify - modifier)
press the icon you want to dock and stay pressed
drag the pressed icon to the dock bar
release the icon.
presse the menu button and choose "save"
here you are... easy !
Note if you want custom icons for dock, see the theming howto.
Launcher TW4.5 : miscellaneous
well... all other points not listed before about the launcher TW4.5 !
>> see here http://forum.xda-developers.com/showpost.php?p=18491558&postcount=6
Launcher TW4.5 : reporting an error, a crash
As TW4.5 crashes, a log file is automatically created here :
Simply report the content of this file in the officiel thread, and write the maximum details about what you wanted to do, what you've done, which phone and which ROM do you use.
Themes : downloading & applying
how to download and to apply, use themes. And what kind of "restrictions" you may encounter.
>> see here http://forum.xda-developers.com/showpost.php?p=18491573&postcount=8
Themes : creation
howto create themes... in a few words (hoping so) !
>> see here http://forum.xda-developers.com/showpost.php?p=18491582&postcount=9
You also can suggest themes to Fr4gg0r easily by filling up this web formular (http://www.i900playeraddict.com/android/TW45/tw45.php) and send an MP to him.
Themes : icon's names
greate debate... how have to be the icon's names for applications? You may find here some listed and tricks to find the names of others.
>> see here http://forum.xda-developers.com/showpost.php?p=18491589&postcount=10
Themes : links of some
not so many themes for now... I'll try to list them here, with printscreens (or not).
>> see here http://forum.xda-developers.com/showpost.php?p=18491594&postcount=11
Themes : miscellaneous
well... all other points not listed before about themes!
>> see here http://forum.xda-developers.com/showpost.php?p=18491605&postcount=12
Miscellaneous items and infos
well... all other points not listed before !
>> see here http://forum.xda-developers.com/showpost.php?p=18491610&postcount=13
Frequently Asked Questions (FAQ)
well... maybe questions which are not answered in all of upper posts !
>> see here http://forum.xda-developers.com/showpost.php?p=18491802&postcount=14
So now... feel free to add suggestions to complete this HowTo !
And... never forget this : THANKS FR4GG0R for this launcher...
Installation of Applications & Widgets
Installation of Applications & Widgets
First of all, your phone have to be ROOTED !
Secondly, I strongly suggest you to have another launcher installed (and defrozed)... this for avoiding a loop reboot and to be able to work, remove,... with applications.
There is two different kind of installations of the Launcher TW4.5.
(note that tw4key.zip is not necessary for installation, it's just for resigning applications)
a. with TW4Manager
b. by hand
Let speak first with the common solution, this with TW4Manager. It's pretty easy :
download TW4Manager from the officiel thread
install it like another application
run it
go in the menu "Check for Updates & Uninstall"
select "TW4 Manager" to be certain to have the very last version installed
That's all for the TW4Manager... so now we will see how to install the TW4.5 Launcher with TW4Manager :
run TW4Manager (think just to check you have the very latest version)
go in the menu "Check for Updates & Uninstall"
if you do not have a "cyanogenmod" ROM, select "latest stable version" by clicking on it
if your ROM is a "cyanogenmod" one, select "latest cyanogenmod" by clicking on it
you now can select to install the lauchner in normal mode (like other applications) in "data/app" or in system mode (like the normal launcher) in "system/app".
That's all !
Note that if you already have one version installed, I strongly suggest you to click first on "uninstall" then on "remove old tw4.5", then on "latest stable version".
Don't forget to backup your homescreen berfore updating the launcher, either with the backup option of TW4.5Launcher (see post about this option), or with another backup application (like Titanium for example).
**** info to come : differences betwen the two installations modes
So now we will see another way of installing, the procedure TW4.5 Launcher "by hand".
if you do not have the TW4.5 installed (and have a Samsung phone or have touchwizz installed) :
go in "system/app"
find "TouchWiz30Launcher.apk" and rename it to "TouchWiz30Launcher.apk.OLD"
find "TouchWiz30Launcher.odex" and rename it to "TouchWiz30Launcher.odex.OLD"
find "TWLauncher.apk" and rename it to "TWLauncher.apk.OLD"
find "TWLauncher.odex" and rename it to "TWLauncher.odex.OLD"
find any other file with "TW" and "Launcher" in the name and rename them with .OLD at the end
if you do not find this files (other phone or touchwizz not installed), don't be afraid... just skip this steps !
if you already have a version of TW4.5 installed :
go in "system/app"
find "TW4Launcher.apk" and rename it "TW4Launcher.apk.OLD" or simply delete it
copy the latest version of launcher you have downloaded in this folder.
if you want to make a really clean new installation of your launcher, you also can rename "data/data/samsung.tw4.nextgen" folder in (for example) "samsung.tw4.nextgen.OLD", do the same for "sdcard/.TW4Themes" folder to "sdcard/.TW4Themes_OLD" (or delete it) and relaunch the launcher.
The new folder, with default settings, will be created.
Last points... installing the Widgets.
First to know that special widgets needs to :
- have a samsung framework
- have been resigned to be functionnals with TW4.5 Launcher
You also can download some widgets (resigned) for SG1 and SG2 via TW4Manager and "Widgets" :
run TW4Manager (think just to check you have the very latest version)
go in "Widgets"
select the system you want (SG1 or SG2)
a list of available resigned widgets will be shown
check the one you want
hit the "Menu" button
choose "apply selected"
The widgets will be installed.
Note that:
- Power Widget stays gray on samsung firmwares (it does not on cm7 for example), after reboot it will be displayed normally.
- some widgets listed will not be functionnals on some systems.
- not all widgets are listed. Scroll the official thread to find more (and report links so I can put the links here)
- on my SG2 quite all other widgets are functionnals (not all of Samsung)
- some widgets, even if resigned, will absolutely not work on some phone. So sad... but take other widgets, sorry !
- if you have some widgets which are absolutely working, please send me a PM with the widget's name, your phone (and ROM) and, of course, a downloadable link so I will upgrade the infos
That's all for now... but if you have any other clues or infos, PM me or post an answer !
Launcher TW4.5 : installation problems
Launcher TW4.5 : installation problems
well... sometimes it's hard to function and some Force Close (FC) occurs. Mainly you can avoid this by doing a really proper new installation.
Steps to do so :
install another launcher
go in "data/data/"
rename "samsung.tw4.nextgen" folder in (for example) "samsung.tw4.nextgen.OLD", or simply delete it
go in "system/app"
find "TW4Launcher.apk" and rename it "TW4Launcher.apk.OLD" or simply delete it
go in "sdcard"
rename "sdcard/.TW4Themes" folder in (for example) "TW4Launcher.apk.OLD" or simply delete it
execute TW4Manager and:
go in "Check for Updates & Uninstall"
click on "uninstall" (redondant with the above points, but to be certain)
click on "remove old tw4.5" (redondant with the above points, but to be certain)
click on "latest XXX version" (depending of your ROM)
wait until confirmation of installation
reboot your phone (it's why it's better to have another launcher installed)
execute/relaunch the launcher. New folders, with default settings, will be created.
That's all for now... but if you have any other clues or infos, PM me or post an answer !
Launcher TW4.5 : actions on screen
Launcher TW4.5 : actions on screens
This Launcher acts quite the same as the touchwizz 3.0 launcher. But I will explain you here how to do some little actions on the main screen.
set default screen
you quickly can know which is the main screen by :
- pinching in on the screen (or by hitting menu and then configure). A list of all desktops will appear :
The default mainscreen is the one with the little house drawed on it.
To change the default homescreen, from this view:
- hit the menu key
- click on "define as default homescreen"
- select the one you want. It will be greyed
- click on "ok"
adding screens
- pinching in on the screen (or by hitting menu and then configure). A list of all desktops will appear :
- press the + button to add a new screen
removing screens
- pinching in on the screen (or by hitting menu and then configure). A list of all desktops will appear :
- press and hold the screen you want to remove
- drop the holded screen in the bottom trash bin
- validate
change the size of widgets
press long the widget until the phone make a little vibration. then stop pressing. You will see a yellow grid allowing you to resize the widget by dragging the grey corner :
quickly select a screen
you have many options to quickly select a screen :
- if you're not on the main screen, simply hit the middle button to go back to main screen
- hit the "pageIndicator" of the page you want to reach
- slide the "pageIndicators" to quickly browse screens
basis functions
adding new shortcuts, change wallpaper, adding widget, moving shortcuts and widgets through screens,... are like the TW3.0
Just to note that if you have themed applications, shortcut of those which are dragged from the appdrawer will have the themed icon.
That's all for now... but if you have any other clues or infos, PM me or post an answer !
Launcher TW4.5 : preferences
Launcher TW4.5 : preferences
To acces preferences, from Homescreen : "Menu" >> "Preferences" to have this screen :
Here are the options, with details, you can use to configure the launcher :
homescreen settings
paramètres par défaut et principaux.
homescreen looping = allow you to loop screens. It means when you reach the last right one, you keep swyping and you come to the first left. The same for the other "way".
wallpaper scrolling = allow your wallpaper to "follow", move with selected screens. Or not.
landscape mode = activate landscape mode. Rebooting the phone is necessary, not only the application.
workspace rows = number of workspace rows. Note that some widgets may not display all infos.
overshoot value = this is the "elastic"effect in changing screens. By default set to 15. Set it to 0 to avoid elastical effect.
app labels = under shortcuts, show applications names
indicator auto hide = hide automatically (or not) after some seconds the pageindicator (screen indication) picture, which allow you to know/select screens
indicator numbers = hide or show the screen number on the pageindicator (screen indication)
nb: to define the number of screens, you have to pinch in from the homescreens, no more in the preferences.
app drawer
options to see, arrange,... the list of applications.
row count = the number of rows in the applications grid (1 to 6)
column count = the number of columns in the applications grid (1 to 6)
sort order = order of applications (without or alphabetical). In the version #21 and earlier, the folders are listed following the name, not first.
overshoot value = this is the "elastic"effect in changing pages. By default set to 15. Set it to 0 to avoid elastical effect.
app backdrops = show the tiles (pictures) in background of applications
app 3d effects = show the applications in a kind of 3D view. Only available with "App Backdrops" enabled.
3d transition effect = kind of 3D transition in changing pages
running apps = show a dot (default red) on upper corner of running applications
dock settings
Settings for icons in the bottom bar (dock).
uninstall button = show (or not) the little button allowing to uninstall the application putted in the dock
icon dock count = number of icons in the dock (1 to 5). Note that the icon to go to appdrawer will count for one and that you can't remove it. So you could add from 1 to 4 additionnal icons.
dock labels = show (or not) the names of applications docked
centered apps icon = if selected, the icon to go to appdrawer will be centered on the dock. Else it will be on the right side.
swipe actions = allow you to choose a second behaviour for each of the five icons in the dock bar, handled by swiping over the icon (from icon to screen).
nb: to avoid having a dock background (the one with grass is by default), you need do make at least one theming action, by adding a transparent file called dock.png (480x80 pixels) in the folder ".TW4Themes/currentTheme" folder.
badge counter
informations about number of unread SMS, mails,...
unread gmail counter = allow to show unread messages from gmail application. Notice that this is greyed for samsung roms.
gmail accounts = allow you to choose the gmail accounts which have to show indicator. Needs that "unread gmail counter" is checked
unread sms counter = show (or not) the circle with number of unread messages, this for non Samsung ROMs. For samsung's rom, indicators are always shown.
system settings
stay in ram = allow you to let the launcher stay in RAM. Quicker if checked
themes
Themes gestion and handling. Themes can be downloaded with TW4Manager.
current theme = the actual theme
choose theme = select a theme form those installed
install theme = install a new theme by copying it from the root folder to the theme folder. This is mandatory to be certain to find the theme in the theme list.
As you install a new theme, you will have two choices :
- Merge = the new theme will copy his icons in the folder, but the icons of the former theme, which are not in the new one, will stay and be displayed
- Overwrite = the application will first totaly empty the folder of the theme, then will install the new theme. You so will not have some icons of old theme
backup & restore
this allow you to backup and to restore all infos (folders, preferences, shortcuts, widgets,...). This is important to do if you intend to install a new version.
Note that it's for now (version #21) only one backup. You may find this backup in ".TW4Themes/bakcup" folder.
restart and save
This menu is a little down on the screen. This is MANDATORY to validate the modifications you made and to restart the launcher.
You also can save and restart by pressing the Menu button.
donate -- version XX
allow you to donate some bucks to fr4gg0r. And, of course, allow you to know the version of the TW4.5 Launcher
That's all for now... but if you have any other clues or infos, PM me or post an answer !
Launcher TW4.5 : miscellaneous
[ more to come... very soon ! Thanks to be patient, texts are on the move... ]
Launcher TW4.5 : widgets
[ more to come... very soon ! Thanks to be patient, texts are on the move... ]
Meanwhile, if you have some widgets which are absolutely working, please send me a PM with the widget's name, your phone (and ROM) and, of course, a downloadable link so I will upgrade the infos.
thanks in advance !
Themes : downloading & applying
Themes : downloading and applying
Once again, it's kinda pretty easy to have themes for our TW4.5 Launcher.
How it works ?
A. Downloading themes
You have two choices:
a. with tw4manager
b. by "hand"
Let's begin with the common way, with tw4manager
download TW4Manager from the officiel thread (if not already done), install it like another application and run it
go in the menu "Themes"
you will see a list of available themes.
click once over the theme you want and you will have two choices :
View = to see the thread on XDA which will give you more details
Download = to download the theme directly to your mobile
if you download a theme, it will be downloaded directly in the Theme directory of TW4.5 Launcher
To refresh the themes list, hit the "Menu" button and choose "Refresh themes list".
If you choose to download a theme "by hand", because for example the theme isn't listed in the theme list, do the following :
Download the theme you want. Beware that it's in .zip format !
copy this .zip file in the folder ".TW4Themes" on your mobile
Note that if you can't see the folder ".TW4Themes" in your file explorer, you simply can copy the .zip file of the theme in the root directory. But in this case, you will have, in the installation process, to first import the theme to be able to enable it.
A. Installing themes
Here you have to use the TW4.5 Launcher itself for doing this.
button "Menu"
then "Preferences"
choose the menu "Themes" in the list
you now have 3 infos :
"Current Theme" = the actual installed theme (which is in the ".TW4Themes/currentTheme" folder)
"Choose Theme" = allow you to choose an installed theme (on your phone)
"Install Theme" = allow you to install a theme, meaning moving the .zip files from the root [of your phone] to the ".TW4Themes" folder
as you click on "Choose Theme", a list of available themes will drop down
select the one you want and the hit "Apply"
you will have a question to answer :
"Overwrite" = will first delete the content of the ".TW4Themes/currentTheme" folder, then put the new theme in.
"Merge" = will only install the new theme, without deleting old theme before. This can be very usefull if you want to keep icons which are not in the new theme.
Save and restart TW4.5
Note that you always can break the procedure by hiting the "back" button.
Themes : creation
[ more to come... very soon ! Thanks to be patient, texts are on the move... ]
Meanwhile, you still can read Fr4gg0r's post on theming : http://forum.xda-developers.com/showpost.php?p=18185593&postcount=2173
By the way, I also made a very little webformular to quickly have a correctly sentenced ligne for sending the correct typo to Fr4gg0r so he could easy put it on the themes list :
1. fill this webform with infos : http://www.i900playeraddict.com/android/TW45/tw45.php
2. clic on "Send"
3. on the new opened webpage, click the button to copy the text
4. send it via MP to Fr4gg0r or post in his thread
Thanks in advance !
Themes : icon's names
Themes : icon's names
Well... great subject !
So, basically, we have three kind's of icons :
a- those on the application's drawer
b- those on the dock (bottom of screen)
c- those on the mainscreens
A. Application's drawer Icons
It's very easy to have you own icons (instead of originals).
The icon size should be 72x72 (or higher) so that the icon does not get upscaled.
Name the icon either <packageName>.png or <className>.png.
TW4.5 will first look for the <className>.png then if not found, for the <packageName>.png. This means <packageName>.png" is more convenient as long as the app does not have multiple icons in the appdrawer.
Hiiik... some examples !
- Opera Browser
the package's name is "com.opera.browser", so you have to name the icon "com.opera.browser.png"
- Screen Off and Lock
the package's name is "com.katecca.screenofflock", so you have to name the icon "com.katecca.screenofflock.png"
But there is two shortcuts made, pointing to the same application: one for launching this application, one to use settings. You now have to use the className. And the className, for the settings of this application, is "com.katecca.screenofflock.Setting". So the icon for the Settings's shortcut (different of the other one), will be "com.katecca.screenofflock.Setting.png"
B. Dock Icons
Well... naming icons for the dock (bottom of the screen) is not very complicated. You only have to add "dock_" before the name of the icon (in the appdrawer, as explained before).
So, if you want to dock the shortcut to Opera, the dock icon will be named "dock_com.opera.browser.png" and if you want to dock the ScreenOffLock application (not the Settings), it will be "dock_com.katecca.screenofflock.png".
C. Mainscreens Icons
Since the version #17, all icons which have a "named icon" (see point A upper) will be iconed on mainscreens. If you made an update of an application, the old icon can be restored. Don't worry, just restart the TW4.5 and it will be iconed again (except if the package's name or the class's name has changed!).
So now... the biggest question is the following :
"How is it possible to know the package's name or the class's name of an application ?"
It's quite easy too... Let's starting with the easiest, the package's name.
You have many solutions, here are some :
** Via my web (little) help **
1. from any browser, go to http://www.i9100galaxys2.com/android/names/
2. search the one you need
** Via the Market **
1. open the android market on your computer (or via the webbrowser, not the market's app)
2. go to the page of the application
3. look at the url of the webpage, it will be so (example with Opera) :
Code:
https://market.android.com/details?id=com.opera.browser&feature=search_result
4. take only the infos after the "id" tag and the next "&" symbol, and you will have the package's name. Here it's "com.opera.browser"
** Via Astro File Manager **
1. download the free version of
2. open Astro
3. clic onr "Menu" >> "Tools" >> "Applications Manager"
4. find the needed on in the list
5. hold long on the name until a new windows open
6. on the new windows, look at the line "Name"
** Via TW4.5 itself **
1. button Menu
2. Preferences
3. Dock Settings
4. hit "Action for first icon" (or another one)
5. find the needed on in the list (the apps are not sorted at all)
6. hit the little triangle near the name
7. see the name of the package
8. to be certain (or if the name doesn't work), hit to set and go back
9. see what's written for the icon. The first part (before /) is the package's name
10. write down the name for correctly naming your icon.
nb: do not forget to clean the action by holding long on it.
Well... and now, how to set the class's name.
One of the easiest way is to use TW4.5 itself, or something else like a log reader.
** Via TW4.5 itself **
1. button Menu
2. Preferences
3. Dock Settings
4. hit "Action for first icon" (or another one)
5. find the needed on in the list (the apps are not sorted at all)
6. hit the little triangle near the name
7. read the different possible actions
8. hit the one you want (here for example Settings of ScreenOffLock)
9. see what's written for the icon : "com.katecca.screenofflock/com.katecca.screenofflock.Setting"
The first part (before /) is the package's name.
The second part (after /) is the class's name.
10. write down the name for correctly naming your icon.
nb: do not forget to clean the action by holding long on it.
** Via a logcat **
a bit harder...
1. download a free logcat, like Catlog
2. run catlog. It will save on a .txt file all actions you do
3. launch the shortcut you want
4. stop catlog
5. open the .txt file created (usually in "catlog_saved_logs")
6. search for the line corresponding of the launch/use of your shortcut (of point 3). This line will be like this :
Code:
I/InputDispatcher( 2804): Delivering key to current input target: action: 0, channel '40ca06c8 com.katecca.screenofflock/com.katecca.screenofflock.Setting (server)'
7. you also can read the both infos "com.katecca.screenofflock/com.katecca.screenofflock.Setting"
The first part (before /) is the package's name.
The second part (after /) is the class's name.
8. write down the name for correctly naming your icon.
Examples for making a difference between the "Phone" icon and the "Contacts" icons.
For the contacts icon (red icon with guy's face) :
Code:
com.android.contacts.png
com.android.contacts.DialtactsActivity.png
com.sec.android.app.contact.png
com.sec.android.app.contacts.png
com.sec.android.app.contacts.ContactsEntryActivity.png
com.android.contacts.ContactsListActivity.png
(adding "dock_" before to be able to dock the icon)
for the phone icon (green icon with a phone) :
Code:
com.sec.android.app.dialertab.png
com.sec.android.app.dialertab.DialerActivity.png
com.sec.android.app.contacts.DialerTabActivity.png
com.sec.android.app.contacts.DialerEntryActivity.png
com.android.contacts.DialtactsActivity.png
(adding "dock_" before to be able to dock the icon)
For myself, this two are ok :
for the red contacts icon = com.sec.android.app.contacts.png
for the green phone icon = com.sec.android.app.contacts.DialerEntryActivity.png
tested when I dock icons.
Details here too : http://forum.xda-developers.com/showthread.php?p=18330862#post18330862
Themes : links of some
Themes : links of some
I will try here to set all the themes available for the beloved TW4.5 Launcher. You may find them directly via TW4Manager, as soon as they are added by fr4gg0r, of course.
To know how to install themes, please report here : http://forum.xda-developers.com/showpost.php?p=18491573&postcount=8
You want to quickly report a theme to put it in the TW4Manager? do the following
1. fill this webform with infos : http://www.i900playeraddict.com/android/TW45/tw45.php
2. clic on "Send"
3. copy'n paste the text and send a PM to Fr4gg0r
4. post infos here
And now... some themes !
Please note that download links can change. If so, please refer to the details links. Thanks
StormTroopers
by Corwin9S.
See details here.
The Smurfs
by Corwin9S.
See details here.
Chevrolet
by Corwin9S.
See details here.
SGII 72x72
by Corwin9S. With official SGII icons. Infos in .txt inside.
See details here.
iReflected
by Corwin9S. iPhone like them.
See details here.
Rouages
by Corwin9S. Dark Wheels, with at least 214 packages named icons.
See details here.
Pumpkins Girls
by Corwin9S. Halloween Girls. WP inside.
See details here.
Morrigan Aensland
by Corwin9S. Darkstalkers Figther. WPs ddl from XDA
See details here.
Catwoman
by Corwin9S. CatWoman loves blue diamonds. WP inside.
See details here.
IronMan Big Icons
by Corwin9S. Iron Man complete theme. Wallpaper inside.
See details here.
IronMan Small Icons
by Corwin9S. Iron Man complete theme. Wallpaper inside.
See details here.
Warcraft
by Corwin9S. Follow the Horde or not... WP inside.
See details here.
Transparents, colored backdrops
by Corwin9S. Just tiles for icons in AppDrawer
Download file in attachment.
NoDock!
by Corwin9S. Just not to see dock's picture.
Download file in attachment.
Minimalism
by fr4gg0r. Only dock icons, in minimalistic texts.
See details here.
Click here do download it.
PurityFS
by rafal408
See details here.
Click here do download it.
iPhone folder
by fr4gg0r. Cool iPhone like folder icons
See details here.
Click here do download it.
Updated icons pack for TW Launcher 4.5
by fr4gg0r. These are higher resolution, color icons that take the place of the stock black and white icons that come as default with the launcher.
Click here do download it.
SGS II Theme
by bassie1995. SGS II theme includes A LOT of SGS II app icons, even in your app drawer and CyanogenMod 7.
See details here.
Click here do download the standard version for SG1.
Click here do download the CM7 Version.
Of course, if you create a theme and want that it's listed here, just PM meplease send me a PM with the theme's name, a little description, a link to presentation (if it exist one), of course, a downloadable link so I will upgrade the infos.
Themes : miscellaneous
[ more to come... very soon ! Thanks to be patient, texts are on the move... ]
Miscellaneous items and infos
[ more to come... very soon ! Thanks to be patient, texts are on the move... ]
Frequently Asked Questions (FAQ)
impossible to sort applications in appdrawer, it gives me alot of gaps. when i fill them in manualy then restart touchwiz it returns everything as is.
>>> uncheck the sort order to be "unrestricted".
-------------------------------------------------------------------
well... maybe questions which are not answered in all of upper posts !
So if you have a question in a such of case, ask it and as an answer is found, I will update the HowTo corresponding section and add this here.
thanks in advance !
At time when i press and hold the menu key, i see the latest six apps popup but when i let go the key, it closes. Is there a fix for this?
jaskiratsingh said:
At time when i press and hold the menu key, i see the latest six apps popup but when i let go the key, it closes. Is there a fix for this?
Click to expand...
Click to collapse
which phone and which rom ?
for me, it's when I long press the middle button.
Corwin9S said:
which phone and which rom ?
for me, it's when I long press the middle button.
Click to expand...
Click to collapse
I9003 and both on froyo and GB...Its not always but random
that's a very nice howto, thank you very much.
One thing, you suggest Imageshack as hoster for the preview image of a theme.
Imageshack is not suitable because it does not provide direct download links of the images. One possibility is to rename the .png to .zip and attach it somewhere in the forums and use the attachment-link (of couse you can also keep the .png).
added new theme in list :
Rouages
by Corwin9S. Dark Wheels, with at least 214 packages named icons.
See details here.
Hi
I have a galaxy s2 with this installed but it wont let me sort them properly. it gives me alot of gaps. when i fill them in manualy then restart touchwiz it returns everything as is.
Any help please