DESCRIPTION
This is an initiative that I decided to take to give the possibility to all those users who like to create projects often, and for all those who tend to be aware of the publications of the previous ones.
That is, a project, also designed entirely in Tasker hehe, that you, as developers, will have the possibility to offer everyone else a real-time follow-up of your work, like: content planned to be created, whatever you are currently working, individualized development progress, history of your work, and much more.
But it can also be very useful for those developers who like to keep track of their own projects. (I include myself)
Main features:
· Real time updates.
· Automatic and manual checks for changes. (client side)
· Be aware of dev's current, planned and archived projects.
· Dedicated history section, with all dev's work.
· Basic log based on date and time (UTC) for dev's actions.
· Classify content by: name, type of content (project, task...), description, dedicated changelog, and more.
· Statusbar notifications for upload/download process of DB files, for both devs and clients, respectively.
· Include screenshots and download links for all your projects
(new)
· Stay in touch with your followers in a more direct and personalized way, thanks to the new broadcasting messaging system.
(new)
Setup:
- Client...
You as a follower of the developer's projects, these are the things you have to configure in your project:
1. Take and open the GDrive (
PC or
Android) link that the developer will provide to you, and add the folder (not the file) that will appear, to your account. (use the '
Add to My Drive' option)
2. In the project, use the '
TPTB - Setup (UI)' and '
TPTB - Setup (GDrive)' tasks to configure it.
3. That's all!
- Developer...
You as a developer of your projects, these are the things you have to configure in your project:
1. Go to your GDrive (
PC or
Android) account, and create the directory/directories where you want Tasker to store the DB file.
2. Create a share link for the last, if multiple, available directory as: 'Can View' (only).
3. Then, share that link with your users. (as mine below)
4. In the project, use the '
TPTA - Setup (UI)' and '
TPTA - Setup (GDrive)' tasks to configure it.
5. That's all!
Notes:
- Thanks to @Universo for helping with the SQL statements.
- A working GDrive account, for both the client and developer, will be needed to use this project.
- Do not use the 'dash + vertical broken bar + dash' (-¦-) expression in any text field. It is used as a column separator during the data extraction process from the database.
- Time from logs are in UTC format, automatically converted from the dev's device. So, take that time format into account, compared to where you are.
- If the original developer of this project (@SmartPhoneLover) considers it necessary to update your databases, due to an internal restructuring of it, the developers have at their disposal the task 'TPTA - Update Database', included in the same project. (Instructions within the same task)
- Due to a limitation by Tasker, everything related to the text of the 'Menu' elements of the 'TPTX_Main' scene, such as: font type, size, color ..., must be edited individually and manually from each from them. Same for 'Spinner' elements.
SCREENSHOTS
CREDITS
@SmartPhoneLover
@Universo
CHANGELOG
- New: Download links (as simple or clickeable text) and screenshots (as pics) for prj/prf/tsk/scn(s) can now be included. (External links are the only soported ones, in other words, raw data (e.g.: binary) cannot be stored into the database directly)
- New: Users can now be aware of a more direct way with the new internal message broadcasting system.
- New: Those scenes that may need to be accessed frequently while editing/previewing info (e.g.: adding download links), can now be restored without loosing any data, or having to reload the whole process. (Use the upper right corner checkbox, if available)
- New: Added time context profile for Dev's version, to allow uploading the DB automatically once a day.
- New: All tabs results are now alphabetically sorted (ASC).
- New: A dot pointer (indicator), just below the 'UPLOAD' button, will tell you if there are changes that you have not shared yet. It will be restored after uploading last changes. (Dev version)
- Fix: The archived content was possible to publish directly. (Dev side)
- Fix: Wrong text position for content information scene on 'ARCHIVED' tab.
- Other: Optimizations on search methods for SQL statements.
- Other: The date and time format for the internal project log can now be customized from 'TPTA - Setup (UI)' task. (Dev version)
- Other: Reworked the whole code of both project versions.
- Other: The value stored into the 'TPTA_temporal' variable when reading db file, was reordered and cleaned up to help developing the project on future versions.
- Other: DB reworked to allow it storing new data type. (Devs will need to use the 'TPTA - Update Database' task to move data from old to new version of the database: Instructions included within the task itself)
- Other: Minor fixes that didn't affect the project functionality, but caused arrays() to be created without a real purpose. So they could hinder the use of it in future versions.
- Other: Changed the way in which some scene elements were working against certain situations, to tell what fields were editable and which ones not (Dev side). And the same for the ones to preview info (Dev and Client side).
- Other: Now the database needs to be read more times per cycle than on v1.0 when we move from one scene to another, but will prevent 'TPTX_temporal' variable of being overloaded (and truncated) if for whatever reason it could reach maximum storage size. It will also help to track what info comes from and goes to when debugging.
- Other: Added missing labels (lots of them), to guide the user what each part of the project does.
* As the database was reworked to allow it to store new data, a full manual clean up of both project versions working directories (/sdcard/Tasker/Resources/*) will be needed. After that, devs and clients, download new 'Resources (ZIP)' file again for v1.1, and place each one where appropriate for each.
* Clients, do not forget to update your project versions too. Or you won't be able to use new features from v1.1 of dev's project!
* Devs: Do not worry about the multiple local child variables (local arrays) that may be created when moving between scenes. Info from db won't be affected, as them will be deleted just after closing (not just hidding) previous scenes. Just take care to not reuse them when developing it.
DOWNLOAD
Client
Project (XML)
Project (TaskerNet)
Resources (ZIP)
Developer
Project (XML)
Project (TaskerNet)
Resources (ZIP)
DOWNLOAD (Ads Supported)
Client
Project (XML)
Project (TaskerNet)
Resources (ZIP)
Developer
Project (XML)
Project (TaskerNet)
Resources (ZIP)
